Help me,, Cannot boot in to recovery - GiONEE Elife E7

Please help needed!!
I'm stuck here for 3 days
Ok I'm going to tell everything I did,,
My Gionee E7 is indian version.
First I rooted my phone with kingo Root.
Than I flashed CWM chinese version.
I upgraded my system to kitkat and changed the recovery to stock.
I used it for a week than some how my music player and gallery were corrupted.
I don't have any rom so I download one but it was in chinese, flashed it to my gionee. than after rooting,,
I flashed the CWM, same I flashed weeks ago
Here my problem started :crying:
The CWM is not starting. I used recoery tool to boot into recovery after boot up it shows black screen. I used every method holding Vol+ and power button but the same result.
than I tired to get back to my stock recovery but it does the same.
flashed many times both recoveries but didn't worked.
I searched a lot and find a TWRP. I flashed it and wow it worked Finally I can boot into recoery mode.
Now I find the Nandroid backup of indian version. I made it a zip and flashed it through twrp.
My phone is back to indian version but its slow, not too much but its slow; camera, gallery and other apps take some time to open. I can't make or rcv phone calls. Now what i did is download the update form System update.
Now i got kitkat rom.zip but twrp failed to install it.
Some one on the internet was saying that its the problem with my Kernel. I have the latest kernel so CWM won't work cuz it uses old kernel and display drivers.
My
android version is 4.2.2
Kernel version is 3.4.0-svn2155
I also got TWRP for lolipop,
and I patched binary_update in my kitkat rom too but TWRP can't flash it
Thats my whooooolllleeeee story. "
I got stuck with this for almost 3 days now I'm damn tired can't do it anymore plz help :crying::crying::crying:

I figured it out by myself
Ok guyz didn't get any help so I figured it out by my self.
I'm posting it here so if anyone gets stuck like me could solve his issue
I used GNQC Download tool and flashed the whole firmware of my cell including, kernel, rom, recovery, boot everything.
Now I'm back to stock indian rom (jellybean) with stock recovery and now I'm going to upgrade to kitkat
I'm new user so I can't posts links just replace the (dot) in the link,
First download stock firmware of Gionee e7 in following link, GNQC download tool and drivers also included in this zip:
www(dot)androidxda.com/download-gionee-stock-rom-models
Just unzip it and follow the instructions on this site:
www(dot)androidxda.com/gnqc-downlod-tool
I didn't slept last night bcuz of this mess now going to sleep whole day :silly:
Goodnite and bless you all :angel:

AkashX4686 said:
Ok guyz didn't get any help so I figured it out by my self.
I'm posting it here so if anyone gets stuck like me could solve his issue
I used GNQC Download tool and flashed the whole firmware of my cell including, kernel, rom, recovery, boot everything.
Now I'm back to stock indian rom (jellybean) with stock recovery and now I'm going to upgrade to kitkat
I'm new user so I can't posts links just replace the (dot) in the link,
First download stock firmware of Gionee e7 in following link, GNQC download tool and drivers also included in this zip:
www(dot)androidxda.com/download-gionee-stock-rom-models
Just unzip it and follow the instructions on this site:
www(dot)androidxda.com/gnqc-downlod-tool
I didn't slept last night bcuz of this mess now going to sleep whole day :silly:
Goodnite and bless you all :angel:
Click to expand...
Click to collapse
Hello my friend, please help me.
I am trying to flash stock inidan rom 4.2 but.. I installed all CWM for E7 found on the internet and I am getting black screen. I managed to Install TWRP but TWRP cannot flash the rom that I need to flash. I flashed a chinese 4.2 but is piece of garbage..
gngc-download-tool said that the com port is closed.
I have windows 64 is this the problem causing gngc not working?

No its not, it is working on 64bit windows very well.
In TWRP factory reset and format system and data, than install
Chinese 4.2 ROM. After that boot it and try it again.
It should work!

bllkarv said:
Hello my friend, please help me.
I am trying to flash stock inidan rom 4.2 but.. I installed all CWM for E7 found on the internet and I am getting black screen. I managed to Install TWRP but TWRP cannot flash the rom that I need to flash. I flashed a chinese 4.2 but is piece of garbage..
gngc-download-tool said that the com port is closed.
I have windows 64 is this the problem causing gngc not working?
Click to expand...
Click to collapse
For me...problem!

thereĀ“s a cwm recovery that flashes over the kernel...
i flashed it and than i was unable to go to recovery, every time i tried the phone power off
Solution: Flash the stock boot.img
Use the file according to the Android version...

Help
I just rooted my gionee elife e7. Flashed the chinese recovery which seemed to be the only one which would be compatible. But, while changing a few setting using pimp my rom, the software just stopped working. Errors keep showing up on the screen - "system.ui is not working", "android app is not working", I cannot even go the settings because "settings is not working". Third party apps still seem to work, so, whatsap and stuff continue to function. Doing a factory reset or flashing firmware again seem to be the only viable option.
But, when I try to load up the bootloader using the power and volume keys, it gets stuck on the screen showing the gionee logo and it reads 'fastboot mode' in the bottom left hand side corner. So,
a. can you offer any advice which may be useful ?
b. can you share the link from where you got a TWRP recovery which will work on the Elife ?
c. do you have any idea what exactly went wrong here ?
Any help you can provide will be appreciated because, it's my mausi's phone and I will have a very tough time explaining what really went down here.
Regards,

Related

[Q] Blu Life Pure XL soft brick/bootloop. Need help.

I aware that this is E7 section, but I have problem after tried to flash stock rom of a E7 (maybe this is a stupid thing to do)
Blu life pure XL is a rebrand E7, I believe, that's why I use many custom rom of E7 for my pure XL. and after update it to KitKat (using E7 rom of course) It didn't recognize sim card, and I tried to find a way to downgrade it back to 4.2.2
Couldn't find US version stock rom so I went with Gionee E7 stock rom and it's stuck with bootloop state.
I tried some ways :
-Get in recovery mode and use ADB to sideload a Rom -> not works
-Tried to replace stock recovery with custom recovery with fastboot mode -> not works to, cmd keep saying <waiting for device> and nothing happened
The thing is that I stuck with stock recovery of this Rom and can't go any further in this situation.
Any suggestion? please help..
c'on guys, I'm noob and I really need help here, anyone lend me a hand?
Look here:
http://forum.xda-developers.com/showthread.php?t=3133230
altrin said:
Look here:
http://forum.xda-developers.com/showthread.php?t=3133230
Click to expand...
Click to collapse
Thanks for your reply, finally someone replied me.
But I don't care about KitKat or Lollipop anymore, I tried to flash stock rom of E7 for my phone and now it stuck with bootloop, tried several ways but haven't got it work again
God, already planed to buy a new phone, but
Finally 've got out of this situation. It kept bootlooping because my effort to downgrade it to 4.2.2 was completely failed. My last attempt was applying the kitkat update package through ADB sideload, and It's boot up again with KitKat .
Well, I've found the US stock rom for my phone and I want to try to downgrade it to 4.2.2 again, but if it falls through and stuck in bootloop state again, I don't think I can get it back to life with that update package because that package is for Indian rom.
Any suggestion to help me downgrade my phone? Please, guys, I'm novice and completely noob, I really need help.

Lg g2 no os at all

Hi!
First I tell you how I recently messed up my LG G2 D802.
I hadn't had a custom rom for ages and now I wanted to have one (This wasn't the first time. I've done this a lot earlier). I had always had root access, but not custom recovery. So the first thing was to install one and I chose to download Rom Manager from Google Play, and then install ClockWorkMod. So, when I was installing the custom recovery I came up with a problem: something went wrong during the installation (I have no idea why). When I booted the device, white letters and numbers appeared on the top left of the screen, saying something like: "boot certification error" and numbers like "[780] [800]" and so on. The screen went black and the phone didn't load the OS. So I was shocked of course because I had never had such a problem.
So, desperate for trying everything to find the solution, I tried tens of ways to try to fix the problem. Finally I read about thing called SRKTool. So I used it and ended up having TWRP on my device, and no OS at all. I tried to flash CM12 and CM12.1 (downloaded from the official site) but nothing works out. TWRP says that flashing the ROM is succesful but when rebooting the system it doesn't load the OS but it comes back to TWRP Recovery mode - WHATEVER I DO. I can't enter the Download -mode at all. I tried hard reseting (Power + Vol - keys), but once again it boots to the TWRP. I can't understand why the TWRP fails to flash the ROM even though it's saying the process was successful. Or maybe this problem is much more internal - and permanent.
After tens of XDA developers' threads I'm writing this here because I'm in need of help. I want to bring my G2 to back in life. I'm out of ideas. Can you help me? I tried to flash the stock firmware but guess what happened? The installation failed, and the device booted back to TWRP. So all I'm able to do is to use the TWRP Recovery. I appreciate your help. Thank you.
(Ps. I'm sorry if I break the rules by writing a new thread. My problem just seems to be so unique that I couldn't find help anywhere.)
If you have access to twrp than you can do what ever is needed
what twrp version douy you have?
enabel MTP, so you can copy from PC
Spumpkin said:
Hi!
First I tell you how I recently messed up my LG G2 D802.
I hadn't had a custom rom for ages and now I wanted to have one (This wasn't the first time. I've done this a lot earlier). I had always had root access, but not custom recovery. So the first thing was to install one and I chose to download Rom Manager from Google Play, and then install ClockWorkMod. So, when I was installing the custom recovery I came up with a problem: something went wrong during the installation (I have no idea why). When I booted the device, white letters and numbers appeared on the top left of the screen, saying something like: "boot certification error" and numbers like "[780] [800]" and so on. The screen went black and the phone didn't load the OS. So I was shocked of course because I had never had such a problem.
So, desperate for trying everything to find the solution, I tried tens of ways to try to fix the problem. Finally I read about thing called SRKTool. So I used it and ended up having TWRP on my device, and no OS at all. I tried to flash CM12 and CM12.1 (downloaded from the official site) but nothing works out. TWRP says that flashing the ROM is succesful but when rebooting the system it doesn't load the OS but it comes back to TWRP Recovery mode - WHATEVER I DO. I can't enter the Download -mode at all. I tried hard reseting (Power + Vol - keys), but once again it boots to the TWRP. I can't understand why the TWRP fails to flash the ROM even though it's saying the process was successful. Or maybe this problem is much more internal - and permanent.
After tens of XDA developers' threads I'm writing this here because I'm in need of help. I want to bring my G2 to back in life. I'm out of ideas. Can you help me? I tried to flash the stock firmware but guess what happened? The installation failed, and the device booted back to TWRP. So all I'm able to do is to use the TWRP Recovery. I appreciate your help. Thank you.
(Ps. I'm sorry if I break the rules by writing a new thread. My problem just seems to be so unique that I couldn't find help anywhere.)
Click to expand...
Click to collapse
The solution is easy. Download the stock rom for your model and install it with otg cable. The reason cm12 is not booted is because you need jb bootloader or caf bootstacks.
Enviado desde mi LG-D802 mediante Tapatalk
renzo090513 said:
The solution is easy. Download the stock rom for your model and install it with otg cable. The reason cm12 is not booted is because you need jb bootloader or caf bootstacks.
Enviado desde mi LG-D802 mediante Tapatalk
Click to expand...
Click to collapse
cm11 => jb bootloader
cm12, cm12.1 and cm13 => kk bootloader
klemenSLO said:
If you have access to twrp than you can do what ever is needed
what twrp version douy you have?
enabel MTP, so you can copy from PC
Click to expand...
Click to collapse
The current version is 2.8.7.3. Should I try other versions?
Did you solve the issue? Or is it still not allowing you to get into your F/W?
staylecrate said:
Did you solve the issue? Or is it still not allowing you to get into your F/W?
Click to expand...
Click to collapse
Hi!
I tried to install TWRP version 2.6.6.3, but it fails to flash it so I'm stuck with the version 2.8.7.3. All I'm able to enter is just the recovery mode. I can't enter the download mode so I can't flash the stock firmware.
Currently I'm out of ideas. I can't flash any OS, the TWRP fails everytime and creates errors.
Try flash bumped kernel like lp dorimanx then flash bumped bootstak then lp rom like cloudy or stock. Or google this: lg g2 unbrickable now xda ...that work for me

[URGENT]Yureka turned off suddenly and went on bootloop while normal usage

Hello everyone,
Im using my yureka since more than a year...I hav rooted, changed roms, kernels, softbricked, hardbricked and debricked and got rid of such sort of problems by following the posts in xda.
A month ago, i flashed stock rom cm11, rooted and flashed twrp recovery.. It worked good with no problems, but today while iam chatting, my phone freezed all of a sudden and switched off with no cause and thats it...ENDLESS BOOTLOOP!! :crying:
I tried flashing stock rom and other roms too...but same condition...bootloop continues...!! anyone expert or who know how to overcome this problem please help me in reviving my phone back to working...!! :crying: :crying:
anybody please share your knowledge regarding this issue...please suggest me any solution if you can...do what really these forums are meant for...!!
ravi44teja said:
anybody please share your knowledge regarding this issue...please suggest me any solution if you can...do what really these forums are meant for...!!
Click to expand...
Click to collapse
just wipe data,cache,system,dalvik and flash any rom...
or try flashing stock recovery via fastboot and install stock rom
if u are on cm11 use stock recovery for cm11 and flash cm12 rom via cm11 recovery
let me knw if this wrkd
Abhi_569 said:
just wipe data,cache,system,dalvik and flash any rom...
or try flashing stock recovery via fastboot and install stock rom
if u are on cm11 use stock recovery for cm11 and flash cm12 rom via cm11 recovery
let me knw if this wrkd
Click to expand...
Click to collapse
thanks for ur reply buddy...i tried ur suggestion...but didnt work..
actually, when no procedures worked, i myslf hardbricked phone by flashing cm12.1 using kitkat flashtools, its screen gone blank and bricked and then i used the sd card method of debricking mentioned here http://forum.xda-developers.com/yureka/help/guide-unbrick-hard-bricked-yureka-t3303112
it then came upto cyanogen logo and hanging there, i tried flashing cm12.0 and same stuck at cyanogen logo..then i flashed cm11 stock rom, it booted up and switched on...
but now,
(1) wifi not switching on,
(2)Internal memory corrupted and showing error while opening file explorer as "there is no information available for the file system" , "the file or folder was not found" and internal memory not showing in pc..
(3) while opening camera it shows "revert to default file location", "insert SD card before using the camera" and unable to capture photos
(4) while trying to take screenshot, in notification panel it shows "couldnt capture screenshot, couldnt save screenshot, storage may be in use"
(5)sim cards not detecting at all
in cm 12.0 and 12.1, its nomore beyond cyanogen logo...:crying:
Fixied ?
Hell7 said:
Fixied ?
Click to expand...
Click to collapse
not yet bro

rr 7.1.2 without gapps/ recovery mode not possible

Hello xda developers this is my second thread sorry for the first one that i made yesterday, I am having a problem with my lenovo k4 note a7010a48
after rooting successfully I proceed to flash rr 7.1.2 but did not flash the gapps now my problem is how to go back on recovery mode to start over again
I already used the power button followed by the volume up down buttons but it is not working like before it is nougat. I only need to get to recovery mode. Please help and thankyou in advance. More power
Does u have root access now and which version of rr u flashed
yes the phone is rooted already and flashed with rr 7.1.2 only need to open recovery mode which is I have no idea
Contact in telegram app 9032015333 I will tell u
i dont know that or how to do that can you teach me please thank you
I have the same issue. Can't enter into recovery and the phone is unable to start.
Same Issue || Don't Know How To Fix
Hi,
I am searching for a possible solution from a day. But could not find a working solution.
After successfully flashing RR-N-5.8.5 (Android N)
Unable to go into recovery.
PROBLEM DESCRIPTION:
1. When Press Vol Up + Vol Down + Power Up
2. Recovery is not loading up
3. Instead it goes in boot loop
4. Normal boot mode and fast boot mode are working perfectly fine
SOLUTIONS TRIED:
1. Flashing recovery again using fastboot mode
2. Flashing different recovery, i.e updated version of recovery
As all recoveries which were available were for marshmallow version. I am not sure but have doubt as android version is updated so the kernel so do recovery also become obsolete in this case ?
Any help is welcome and appreciated
Thanks
---------- Post added at 05:18 PM ---------- Previous post was at 05:12 PM ----------
jaineshjain said:
Contact in telegram app 9032015333 I will tell u
Click to expand...
Click to collapse
Whole concept of this platform is sharing your knowledge
Don't you think it would be better if you discuss here itself ?
jaineshjain said:
Contact in telegram app 9032015333 I will tell u
Click to expand...
Click to collapse
Whole concept of this platform is sharing your knowledge
Don't you think it would be better if you discuss here itself ?
for fastboot mode and for recovery mode yes i tried it also but thats the problem no recovery mode. I will wait for the solution when it comes i will just store my phone for a while.
Hi Developers,
Is it possible to reset the phone at hardware level? I can't even connect the phone to PC as it keeps on rebooting.
Please note: upgraded to Nougat and wanted to do the second recovery as suggested by mohancm in the post. When the phone rebooted (before flashing the second recovery), the problem started.
Please let me know if any one has a fix/workaround for the issue.
Thanks,
Srihari
1.Download TWRP recovery unzip files.
https://drive.google.com/file/d/0B1CKVcdcbHFPUzFCODVMN0ZfTW8/view
2.Now in folder TWRP\img\ there is the file recovery.img.
3.Download the second recovery for nougat recovery-Nougat.img and put in the TWRP\img folder.
https://androidfilehost.com/?fid=673368273298981920
4.Rename it as the original, recovery.img and replace it.
5.Then connect your phone to usb and select the 3th option from usb debugging message
"Transfer photos(ptp)"
6.run TWRP_Install.bat from TWRP folder
And you are done, had the same problem and I figure this solution, hope it will help.
I cannot locate the transfer photos(ptp)
ok I already done the part I am now on the recovery mode thanks. new problem of mine is after flashing the rom gapps and recovery after reboot it goes back to recovery mode did I miss something on flashing?
ok so i already passed this problem thanks for the help xda community thank you very much but I have this bootloop problem maybe I did a mistake flashing before rebooting sorry i am a noob in this kind of upgrade specially in mobile phones. I will be careful next time after I passed this problem I hope you will help me once again, my phone in bootloop is killing me.
I have same issue... I flashed gapps and my phone is working smoothly... The issue is i can't go into recovery mode... I tried some one tap reboot to recovery apps but all whats happening is phone restarting normally.
For those who can't access recovery mode. You were supposed to flash updated recovery image after flashing rrn rom.
Enter into fastboot mode by using adb shell.
Flash the updated recovery image
Now try rebooting into recovery.
Should work.
Worst case, restore by flashing stock rom using SP flash tools. And then start all over again.
If you face any issues ping me. Even I had faced this issue and fixed it after a lot of struggle. I can try to help you.
Or you could download Official Twrp App directly from play store, then find A3000 (Air Row) in 'select device' and flash that to recovery, (if your phone is rooted) then you are good to go, go to recovery mode and thats all, your twrp is now has been flashed.
Thank me later??
MisledMew said:
Enter into fastboot mode by using adb shell.
Flash the updated recovery image
Now try rebooting into recovery.
Click to expand...
Click to collapse
This really worked for me. Many thanks man.
Well it got me some time to find the right recovery image for my ROM so I decided to give you link for anyone going through the same.
My configuration at that time was: DotOS 1.2 and TWRP 3.1.1 (or so).
On the DotOS thread was enclosed link to wrong recovery image file (or its version was changed as of 28.12.2018) but after small investigation I found this file recovery-mohan-N.img.
Note: This recovery worked for TWRP and Android Nougat and I'm not an expert to suggest this will work for your case either.
Thank you again and have a nice time
firelmnt said:
This really worked for me. Many thanks man.
Well it got me some time to find the right recovery image for my ROM so I decided to give you link for anyone going through the same.
My configuration at that time was: DotOS 1.2 and TWRP 3.1.1 (or so).
On the DotOS thread was enclosed link to wrong recovery image file (or its version was changed as of 28.12.2018) but after small investigation I found this file recovery-mohan-N.img.
Note: This recovery worked for TWRP and Android Nougat and I'm not an expert to suggest this will work for your case either.
Thank you again and have a nice time
Click to expand...
Click to collapse
Glad it helped

[Bootloop] N9005 not booting after frame (display) replacement

Hi,
as the title says, my phone is not booting anymore, after I transplanted the motherboard from a frame with a broken screen into a new frame (from china).
Abbreviations used:
RR => Resurrection Remix 5.8.5
CWM => ClockWorkMod Recovery 6.0.4.6-kitkat
TWRP => TeamWinRecoveryProject 3.2.1-1
I was using RR from the Rock Stable Setup on it before and it worked beautifully.
What happened:
I performed the mainboard-transplantation according to the iFixit guide
I held the power button to boot the phone:
It vibrated
It showed this screen for a couple of seconds
It vibrated
Back to step 1
And that until I removed power.
Then I tried to boot into recovery mode by holding the key combination on boot:
Same as above, but with this bootscreen
Then I tried to boot into download mode by holding the key combination on boot:
The warning to confirm download mode poped up and I got to see this screen.
I connected it to my PC and opened odin 3.09 and it recognized the device.
I tried to get adb and fastboot to see the device, but nothing worked. (In the old frame and before I broke the screen, it would be recognized at this stage)
I flashed TWRP with odin, odin showed the green "PASS!", but booting to recovery still failed.
I proceeded to flash a stock ROM, which had worked when I had issues with RR.
It worked, I went through the Android 5 setup process, enabled debug and connected adb.
adb saw the phone.
I rebooted to recovery and stock recovery booted correctly.
Sideloading anything with adb failed due to signature verification.
I then went back to download mode and flashed CWM successfully.
It now boots into recovery, but whenever I try to flash anything with CWM, it fails showing this screen
Or something similar (the photo comes from flashing RR 5.8.5)
I have both linux and windows properly setup and used both with adb, fastboot and odin (only windows)/heimdal (only linux).
I checked drivers and usb cables.
I opened the phone back up and checked all connections.
But I can't get any version of RR, CyanogenMod or LineageOS on there.
I've searched the internet, but people that have these kinds of problems after replacing parts of their phones, seem to only have driver issues or skipped steps in the manuals of custom ROM installations.
If you have any idea on what I could try or what I'm doing wrong or not doing, please leave an answer.
I'll keep this post updated below here:
(no updates, yet)
Thanks so much in advance
Simon
Your picture shows stock recovery not CWM .
Try flashing TWRP recovery through Odin .
I did flash TWRP and afterwards there was no recovery anymore.
When I flash CWM, I get the recovery shown in the photo.
The stock recovery has a black background and no touch controls for me.
What you saw must have been CWM.
Update: I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS.
The only working OS I have at the moment is a stock android 5.0, which is not all that useful...
If anyone has an idea, why I can't or how I can find out what is causing it, please say so.
I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS. )
What do you mean by ANY ??
Well, exactly that.
Regardless of what zip I flash, I end up with a bootloop.
If I flash a recovery zip, the recovery bootloops, but the OS still boots.
If I flash a custom ROM, I can still boot into recovery fine, but booting normally results in a bootloop.
The only way to get software onto my phone has been via odin and only an old CWM, Philz Touch, TWRP (Version 2.8.7.0 and below) and STOCK Android (Versions 4.3, 4.4.2, 5).
Anything else I have tried so far did not result in an error, but I couldn't boot into it either.
If you have ideas for software I can try flashing, please tell. I really have no idea how to get the damn thing to work again...
What happens when you flash correct stock rom via Odin ??
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
AnyTimeTraveler said:
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
Click to expand...
Click to collapse
In that case phone is OK .
Usual is that user is failing to follow instructions .
Not sure what you mean by fastboot on a N9005 .sounds like not a N9005 .
Personally with TWRP 2.8.70 i would be flashing something like .
https://forum.xda-developers.com/galaxy-note-3/development/rom-magma-nx-rom-t3508672
as its correct TWRP .
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
AnyTimeTraveler said:
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
Click to expand...
Click to collapse
Dear Mate..
Have you solved your problem? I have same problem after transplating N900 frame.
Sorry, I gave up, since I dearly needed a working phone and bought a OnePlus 3 cheaply from ebay second hand. It's been working like a charm and I threw the note into my museum after I softbricked it for the n-th time and couldn't get it out of a bootloop that didn't leave me time to go into Fastboot.
Sorry friend, but I can't help with this.
after reading a lot of similar threads, seems like the hardware is the cause of us not able to update to higher versions of twrp(& custom roms)

Categories

Resources