I was trying to root my Lenovo P2a42 with TWRP and SuperSU V2.76 but then something went wrong and it wouldn't boot up. I then did an advanced wipe and wiped everything using TWRP and now I have no OS, although I can go into TWRP and the Bootloader. Whenether I try to boot up I get the Bootloader. Now I just want to get it back to normal, I have no backups (Cuz I'm dumb). Please help, thanks in advance.
Excabyte said:
I was trying to root my Lenovo P2a42 with TWRP and SuperSU V2.76 but then something went wrong and it wouldn't boot up. I then did an advanced wipe and wiped everything using TWRP and now I have no OS, although I can go into TWRP and the Bootloader. Whenether I try to boot up I get the Bootloader. Now I just want to get it back to normal, I have no backups (Cuz I'm dumb). Please help, thanks in advance.
Click to expand...
Click to collapse
Hey, did you fix this issue? Stuck at same point.
FIXED:
Flashed the stock rom that is floating around three times and it worked.
Flipperdolphin said:
Hey, did you fix this issue? Stuck at same point.
FIXED:
Flashed the stock rom that is floating around three times and it worked.
Click to expand...
Click to collapse
Yeah I fixed it a few weeks back. I did an advanced reset again then got a stock ROM zip transferred from my pc to my lenovo then flashed it with TWRP. Worked just fine although OTAs no longer work (Too happy to care).
Now, I still want to root my device... If you find a way that works could ya let me know? Thanks.
Excabyte said:
Yeah I fixed it a few weeks back. I did an advanced reset again then got a stock ROM zip transferred from my pc to my lenovo then flashed it with TWRP. Worked just fine although OTAs no longer work (Too happy to care).
Now, I still want to root my device... If you find a way that works could ya let me know? Thanks.
Click to expand...
Click to collapse
I still can't root the damn thing, I just don't understand, tried a few different ways and none of them work
Related
Hey, I'm running TWRP 2.5.0.2 [http://forum.xda-developers.com/showthread.php?t=2292565] and after I flashed a new rom [http://forum.xda-developers.com/show...php?t=2301724] and rebooted TWRP is asking me for a password? Just curious if anyone else has had this problem?
Whenever I don't boot into recovery it says encryption failed. it says to do a factory reset and encrypt the device again.
Edit: I was able to get it working again.
I've seen that before, it was the same time that if I tried to create a nandroid it said there was about 700gb in data. After doing resets and such it would still come back. Only way I got it to go away was by flashing back to stock and re-rooting
obsidianfirefly said:
I've seen that before, it was the same time that if I tried to create a nandroid it said there was about 700gb in data. After doing resets and such it would still come back. Only way I got it to go away was by flashing back to stock and re-rooting
Click to expand...
Click to collapse
Thanks, I'm still getting used to how this phone works. Xperia Play was much easier.
Schwabie64 said:
Hey, I'm running TWRP 2.5.0.2 [http://forum.xda-developers.com/showthread.php?t=2292565] and after I flashed a new rom [http://forum.xda-developers.com/show...php?t=2301724] and rebooted TWRP is asking me for a password? Just curious if anyone else has had this problem?
Whenever I don't boot into recovery it says encryption failed. it says to do a factory reset and encrypt the device again.
Edit: I was able to get it working again.
Click to expand...
Click to collapse
So how did you get it working? Happened to me earlier this week. Had to flash to stock.
dwmartin6341 said:
So how did you get it working? Happened to me earlier this week. Had to flash to stock.
Click to expand...
Click to collapse
Sorry, I had to do the same [flash back to stock]. Not sure what caused it to happen though.
Use the verw first version of TWRP
Schwabie64 said:
Sorry, I had to do the same [flash back to stock]. Not sure what caused it to happen though.
Click to expand...
Click to collapse
I got the same problem with my Nexus 7 (2013) when using the lastest version of twrp (v2.6.3.0).
I didn't encounter this issue when I used the very first version: openrecovery-twrp-2.6.0.0-flo.img
can someone tell me how to fix this even i have the same issue
kindrudekid said:
can someone tell me how to fix this even i have the same issue
Click to expand...
Click to collapse
I use this recovery now.
http://forum.xda-developers.com/showthread.php?t=2292112
twrp 2.6.1.0 is asking for password
Hey guys been reading alot of discussion and threads in this site to figure out how am i gonna solve this issue. I really don't why the twrp is always asking for password. I wipe everything from carrier to dalvik cache and selected factory reset but eventually i am still stock to this password. I did try to revert the version of twrp but it wasn't successful. It says "FAILED" after installation. I haven't use my phone (gt-n7100), i think, for a month because of this. I badly need your expertise guys. Thanks. Hoping to hear from this community.
Just as I enter TWRP recovery, it asks for a password. I clearly remember that I hadn't set any password. But there is another option "cancel". On pressing that button I enter the normal functions of TWRP recovery. The password is not creating any problems but I would like to put up on for security. Any help guys?
Has anyone had trouble with any 4.3 ROMs where it boots up once, but if you try and turn it off or reboot it, it will get stuck at the Note 2 splash screen.
I've tried pulling the battery, I've tried multiple nightlies of PAC, the developer didn't have a solution for me. I've also tried AOSPA, all have the same outcome. I've been flashing for years, so I know about fully wiping and all the other precautions. Just hoping someone out there had these issues and may have a solutions so I can enjoy some 4.3 goodness. Thanks
mozes316 said:
Has anyone had trouble with any 4.3 ROMs where it boots up once, but if you try and turn it off or reboot it, it will get stuck at the Note 2 splash screen.
I've tried pulling the battery, I've tried multiple nightlies of PAC, the developer didn't have a solution for me. I've also tried AOSPA, all have the same outcome. I've been flashing for years, so I know about fully wiping and all the other precautions. Just hoping someone out there had these issues and may have a solutions so I can enjoy some 4.3 goodness. Thanks
Click to expand...
Click to collapse
This happen to me. After 3 hours of flashing different rooms. After a full clean wipe and flash it booted. So you got to clear everything internal sd and cache. After that I flashed jediv17 and it booted
The only thing that worked for me was switching for TWRP to CWM recovery.
Thanks for both of your replies. I've tried both of those things, and got nothing. I've wiped everything possible and neither recovery has done much to help.
mozes316 said:
Thanks for both of your replies. I've tried both of those things, and got nothing. I've wiped everything possible and neither recovery has done much to help.
Click to expand...
Click to collapse
I am having the same trouble as well :/
Did you reformat you internal storage and then re-flash the your ROM?
Possible Solution... will update my findings after work
Am having the same problems with 4.3 roms on my Note 2 (VZW)... found a possible solution, or at least it worked for this individual in the T-Mobile forum:
http://forum.xda-developers.com/showthread.php?t=2432544
Please post if it works or not for you... if you get it done before I do. Thank You.
---------- Post added at 12:35 PM ---------- Previous post was at 12:29 PM ----------
Try this forum as well... another successful solution for the same problem:
http://forum.xda-developers.com/showthread.php?t=2423629
If any of these solutions work for you, please thank the individuals in the postings that suggested them. Good Luck!
had the same problem, updated twrp and cwm to the latest, and downloaded the latest supersu.zip and flashed it along with the rom, and i've been fine since
Question...
Jjleininger said:
had the same problem, updated twrp and cwm to the latest, and downloaded the latest supersu.zip and flashed it along with the rom, and i've been fine since
Click to expand...
Click to collapse
I already have the latest TWRP but are you using the CWM from the play store? Also, where can I find supersu.zip (is that the CWM superuser?)
m.jude.m said:
I already have the latest TWRP but are you using the CWM from the play store? Also, where can I find supersu.zip (is that the CWM superuser?)
Click to expand...
Click to collapse
download rom manager from the store, and theres the option to download the latest recovery in there. if it doesnt work then you can search for the zip of that version 6.0. something.
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
thats the latest supersu and its zip so you can do it through recovery. once i got 4.3 working with cwm i was able to go back to twrp
hi guys.
i tried installing cf root but that made my phone crash.
tried rooting through TWRP recovery but that also made my hone crashed.
zocex said:
hi guys.
i tried installing cf root but that made my phone crash.
tried rooting through TWRP recovery but that also made my hone crashed.
Click to expand...
Click to collapse
No way currently.
muniz_ri said:
No way currently.
Click to expand...
Click to collapse
How long you think we should wait till we see such a thing happen?
zocex said:
How long you think we should wait till we see such a thing happen?
Click to expand...
Click to collapse
No way of knowing but I suspect that @Chainfire will work on an updated SuperSu at some point.
zocex said:
How long you think we should wait till we see such a thing happen?
Click to expand...
Click to collapse
I didn't test it to much since my goal was to get back down to kitkat I had enough of lolipop after 5.0.1 so when 5.1.1 hit I hit my breaking point with it.
When I flashed the MK2 loader + Modem than flashed custom recovery and than flashed the "UPDATE-SuperSU-v2.37.zip" than flashed back to OD1 loader+Modem to boot back into 5.1.1 to backup some stuff Root seemed to be working. The SuperUser app didn't showup anywhere outside of the app manager but Titanium backup asked for root I granted it and it's root functions seemed to work perfectly.
Random glitch for me? Maybe, I thought about testing it out more but really I was in a rush to get back to KitKat. XD
ccdrop said:
I didn't test it to much since my goal was to get back down to kitkat I had enough of lolipop after 5.0.1 so when 5.1.1 hit I hit my breaking point with it.
When I flashed the MK2 loader + Modem than flashed custom recovery and than flashed the "UPDATE-SuperSU-v2.37.zip" than flashed back to OD1 loader+Modem to boot back into 5.1.1 to backup some stuff Root seemed to be working. The SuperUser app didn't showup anywhere outside of the app manager but Titanium backup asked for root I granted it and it's root functions seemed to work perfectly.
Random glitch for me? Maybe, I thought about testing it out more but really I was in a rush to get back to KitKat. XD
Click to expand...
Click to collapse
Wow thank you man . I am going to try this, I hope it work for me as well
Has anyone had any luck so far?
Hi all,
I recently got a new Axon 7 (A2017U) and wanted to root it just like my old G3. I tried following DrakenFX's instructions (Here: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), but I got lost. I ended up with a password being requested at the android startup screen. In a panic, I clicked Format Data when I got back into TWRP, that made it worse and I went into EDL to see if that might help. Eventually I got back into TWRP and that's where I am now, desperately trying to get my new phone working again. All the threads I read only add another layer of confusion. Would someone be willing to walk me through the steps of fixing my phone? I really don't want to RMA/have $400 to go down the drain. I'd own you a big one.
-RG
video_dewd said:
Hi all,
I recently got a new Axon 7 (A2017U) and wanted to root it just like my old G3. I tried following DrakenFX's instructions (Here: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), but I got lost. I ended up with a password being requested at the android startup screen. In a panic, I clicked Format Data when I got back into TWRP, that made it worse and I went into EDL to see if that might help. Eventually I got back into TWRP and that's where I am now, desperately trying to get my new phone working again. All the threads I read only add another layer of confusion. Would someone be willing to walk me through the steps of fixing my phone? I really don't want to RMA/have $400 to go down the drain. I'd own you a big one.
-RG
Click to expand...
Click to collapse
Hi,
so you have access to the TWRP. Thats good. Do you have access to a stock ROM from your manufacturer? In case yes, you could simply flash the stock.
For this, the rom has to be on a SD card or on the internal memory of the phone.
In TWRP go to "Install", than navigate to the file and swipe to install (it comes a zip file).
mugel2110 said:
Hi,
so you have access to the TWRP. Thats good. Do you have access to a stock ROM from your manufacturer? In case yes, you could simply flash the stock.
For this, the rom has to be on a SD card or on the internal memory of the phone.
In TWRP go to "Install", than navigate to the file and swipe to install (it comes a zip file).
Click to expand...
Click to collapse
I'm looking for one. Some threads pointed to an OTA update that ZTE has on their site. However, when I try to install things on TWRP, I get an error about "dev/block/sde14" being read-only. (It sometimes says "sde13" too.)
video_dewd said:
I'm looking for one. Some threads pointed to an OTA update that ZTE has on their site. However, when I try to install things on TWRP, I get an error about "dev/block/sde14" being read-only. (It sometimes says "sde13" too.)
Click to expand...
Click to collapse
Dis you go on Advanced
Wipe dalvik-chace
Wipe /cache
Do you have access to fastboot?
mugel2110 said:
Dis you go on Advanced
Wipe dalvik-chace
Wipe /cache
Do you have access to fastboot?
Click to expand...
Click to collapse
Yes and I'm not sure. I can boot to system, recovery, and bootloader.
video_dewd said:
Yes and I'm not sure. I can boot to system, recovery, and bootloader.
Click to expand...
Click to collapse
I am far from being a pro. I once had the problem that I was caught in bootloop and could not install a new rom. But I was able to re-flash TWRP (via Minimal adb and fastboot) and than everything was fine.
Maybe someone else can comment on that. On your own risk...
Just a tip. Never panic and press any button
mugel2110 said:
Just a tip. Never panic and press any button
Click to expand...
Click to collapse
I figured haha
i successfully flashed twrp on my a10 yesterday thanks to the help of some users on here. the plan was and still is to rpelace the os with a non google one. everything went ok. the phones was and still is oem unlocked, the phone reports as it did yesterday that there was a none samsung offical software on there so i assume twrp is still present for but for some reason i can't boot into it. booting with power and volume up goes into the old recovery men with no mention of twrp, and the volume up/down boot goies into the old download menu. do i need to reflash twrp or am i missing something?
Much gratitude to you.
you somehow managed to install the stock recovery image? just re flash TWRP but get it from official website
BrotherBoard said:
you somehow managed to install the stock recovery image? just re flash TWRP but get it from official website
Click to expand...
Click to collapse
apparently the phone isn't rooted. i need to root it.
fjb59 said:
apparently the phone isn't rooted. i need to root it.
Click to expand...
Click to collapse
good luck
BrotherBoard said:
good luck
Click to expand...
Click to collapse
i'll need to figure out how to do that. i think i found a link on here somewhere