FORUMS

Optimize Battery Life with This Useful App

Battery life is an important aspect of your smartphone, especially if you use it for more … more

The OnePlus 2 & The Year of Smartphone Compromises

We are very close to entering the last third of 2015, and we have now seen many of … more

OnePlus 2 Teardown, Major Android Vulnerability – XDA TV

The OnePlus 2 has been officially released. That and much more news is … more

What Do You Think About Fingerprint Scanners?

More and more phones are featuring fingerprint scanners, and with many promising … more

"fastboot reason fall through normal boot mode" error port

11 posts
Thanks Meter: 1
 
By gaby-s, Junior Member on 1st June 2014, 04:12 PM
Post Reply Subscribe to Thread Email Thread
Hello,

I'm trying to port Flyme OS (KK) using this thread. But after flash I have this error : "fastboot reason fall through normal boot mode". Can someone help me with this? Thank you

PS: It's in the wrong section sorry...
Last edited by gaby-s; 1st June 2014 at 04:20 PM.
 
 
yeshwanthvshenoy
1st June 2014, 11:42 PM |#2  
Guest
Thanks Meter: 0
 
More
Quote:
Originally Posted by gaby-s

Hello,

I'm trying to port Flyme OS (KK) using this thread. But after flash I have this error : "fastboot reason fall through normal boot mode". Can someone help me with this? Thank you

PS: It's in the wrong section sorry...

it is due to bad boot.img and incompatible init.d scripts.
2nd June 2014, 08:33 AM |#3  
OP Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by yeshwanthvshenoy

it is due to bad boot.img and incompatible init.d scripts.

I tried to decompile and recompile manually the boot.img so it should work no? I'll check compatibility with init.d

EDIT : boot.img is the same as CM11 (changed Bootclashpath) and I put init.d from CM. I have just seen that but my boot.img is 5.2 mb and CM boot.img is 6.3mb, problem while repack?
Last edited by gaby-s; 2nd June 2014 at 09:07 AM.
yeshwanthvshenoy
3rd June 2014, 04:16 AM |#4  
Guest
Thanks Meter: 0
 
More
Quote:
Originally Posted by gaby-s

I tried to decompile and recompile manually the boot.img so it should work no? I'll check compatibility with init.d

EDIT : boot.img is the same as CM11 (changed Bootclashpath) and I put init.d from CM. I have just seen that but my boot.img is 5.2 mb and CM boot.img is 6.3mb, problem while repack?

dont repack boot.img let it be the same as it was in cm11 just put it in ur zip replace the old one and delete the init.d folder already existing and replace with one from cm11!
3rd June 2014, 08:07 AM |#5  
OP Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by yeshwanthvshenoy

dont repack boot.img let it be the same as it was in cm11 just put it in ur zip replace the old one and delete the init.d folder already existing and replace with one from cm11!

Moto g get stuck on boot loader logo
yeshwanthvshenoy
3rd June 2014, 02:25 PM |#6  
Guest
Thanks Meter: 0
 
More
Quote:
Originally Posted by gaby-s

Moto g get stuck on boot loader logo

seems strange perhaps u tried replacing modules and libandroidruntime.so from lib folder?
4th June 2014, 01:38 PM |#7  
OP Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by yeshwanthvshenoy

seems strange perhaps u tried replacing modules and libandroidruntime.so from lib folder?

I'm not sure but I'll look at this
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes