Hello guys. First of all I want to apologize for my English , and the second thing is that I need your help. A couple days ago I tried to flash a custom rom with data2sd to my prime and I've made a mistake that bricked my tablet. I have updated the bootloader to 4.2.1 and I've installed an incompatible TWRP by mistake Now my tablet does not boot OS...only TWRP. The major problem that whatever I try to it gives me that E: unable to mount data(also cache, internal storage, staging) looks like my internal memory failed..and my sdcard is recognized as "system" folder in TWRP file manager. I can access bootloader but there are only 3 icons( recovery, Cold boot, wipe) but no fastboot. Can somebody help me solve this problem?:crying:
motorom said:
Hello guys. First of all I want to apologize for my English , and the second thing is that I need your help. A couple days ago I tried to flash a custom rom with data2sd to my prime and I've made a mistake that bricked my tablet. I have updated the bootloader to 4.2.1 and I've installed an incompatible TWRP by mistake Now my tablet does not boot OS...only TWRP. The major problem that whatever I try to it gives me that E: unable to mount data(also cache, internal storage, staging) looks like my internal memory failed..and my sdcard is recognized as "system" folder in TWRP file manager. I can access bootloader but there are only 3 icons( recovery, Cold boot, wipe) but no fastboot. Can somebody help me solve this problem?:crying:
Click to expand...
Click to collapse
With the 4.2.1 bootloader you are in fastboot as soon as those icons appear. You do not need to select anything.
Most people who have done what you have done are hard bricked but try and fastboot the correct twrp back onto the device.
It normally says sending and then writing but freezes straight after and you can't continue.
flumpster said:
With the 4.2.1 bootloader you are in fastboot as soon as those icons appear. You do not need to select anything.
Most people who have done what you have done are hard bricked but try and fastboot the correct twrp back onto the device.
It normally says sending and then writing but freezes straight after and you can't continue.
Click to expand...
Click to collapse
I've founded a tool WSG_UnBricker_V1.0.3 and I tried to use it. The result is not good at all. Power+ vol.down gives me the menu with the 3 icons but when I'm pushing one of them I'm getting a error "unrecoverable bootloader error(0x00000000)" this is it you think? Garbage is the best place for my Prime now?
motorom said:
I've founded a tool WSG_UnBricker_V1.0.3 and I tried to use it. The result is not good at all. Power+ vol.down gives me the menu with the 3 icons but when I'm pushing one of them I'm getting a error "unrecoverable bootloader error(0x00000000)" this is it you think? Garbage is the best place for my Prime now?
Click to expand...
Click to collapse
You have now killed it completely. I said to try and fastboot the correct twrp as that was your only chance.
Don't thow it in the garbage!
I have the same issue. First, did you enable nvflash? And if so do you still have your backup files? If you said yes to both of these questions you can still save your prime using Craig gomez's nvflash unbrick tutorial. I recommend you use the linux version's automated restore.
http://rootzwiki.com/topic/35086-guide-nvflash-general-users-guide-unbrickrecoverdowngradeupgrade-tf201/
Good luck!
blade2k11 said:
I have the same issue. First, did you enable nvflash? And if so do you still have your backup files? If you said yes to both of these questions you can still save your prime using Craig gomez's nvflash unbrick tutorial. I recommend you use the linux version's automated restore.
Good luck!
Click to expand...
Click to collapse
thank you for trying to help me but it looks like my Prime is bricked forever...I'm new in this things and I didn't enable nvFlash before messing up my device, and of course I don't have the required files to unbrick it. I will wait a little bit maybe a solution will appear after a while...if not then my Prime will be sold for parts on ebay(( I still can't believe that I killed it by making a stupid little mistake...
Related
I recently bricked my asus transformer prime by formatting data, system, and cache without checking if I had a rom on my sd card. Without the option in CWM to install from a rom real sd card I tried to install TWRP and now I have no recovery and the screen hangs at Eee Pad splash screen. I still have the ability to use fastboot. If anyone can unbrick my transformer for me I will pay you.
iamnot said:
I recently bricked my asus transformer prime by formatting data, system, and cache without checking if I had a rom on my sd card. Without the option in CWM to install from a rom real sd card I tried to install TWRP and now I have no recovery and the screen hangs at Eee Pad splash screen. I still have the ability to use fastboot. If anyone can unbrick my transformer for me I will pay you.
Click to expand...
Click to collapse
Show me the money lol
Only joking, on the screen where the fastboot icon is you have a line in the top left with bootloader written in it and a long number at the end. It either starts with a 9 or a 10. What is it?
Sorry for the delay had to take one last final, I'm not sure the device has been on all since it will not turn off so I am currently charging it. I will let you know in 30 mins or so.
9.4.2.15
iamnot said:
9.4.2.15
Click to expand...
Click to collapse
Ok, you are on the ICS bootloader at the moment. The first thing we are going to do is flash a version of TWRP recovery on there which will allow you to install a rom off the external SD.
Power off the prime and put yourself into fastboot mode by holding power button and volume down the same time until a few icons appear on the screen. At this point press volume down to go over to the usb icon and then press volume up. It will look like the prime has frozen. Plug the prime into pc and make sure you have the drivers installed. If you do not please install them from here. http://forum.xda-developers.com/showthread.php?t=1426502
Next follow this post to flash ICS twrp http://forum.xda-developers.com/showpost.php?p=34477681&postcount=5705
Only use the file in that link to install it while on ICS bootloader. Later on you are going to flash hairybean 1.51 which will take you up to Jellybean Bootloader. If you use this file after that you will brick your tablet.
You should now be able to boot into recovery again.
Go to the second post here http://forum.xda-developers.com/showthread.php?t=1674827 and follow the "Upgrade Instructions for ICS"
Let me know how it goes.
Thanks for all the help my tablet is back up and running,I finishing the androwook install now.
iamnot said:
Thanks for all the help my tablet is back up and running,I finishing the androwook install now.
Click to expand...
Click to collapse
That will be 200 dollars please.. lol
Glad you're all back up and running mate.
flumpster said:
That will be 200 dollars please.. lol
Glad you're all back up and running mate.
Click to expand...
Click to collapse
the guy didn't even press thanks for ya!
This kinda happened to me. Just download the program to flash TWRP. It's somewhere in XDA. I can link you when I get home. Just put it into fastboot, and USB mode and start the program, and it will flash TWRP. Then use an SD card and put the ROM on it and flash
aznflawless said:
This kinda happened to me. Just download the program to flash TWRP. It's somewhere in XDA. I can link you when I get home. Just put it into fastboot, and USB mode and start the program, and it will flash TWRP. Then use an SD card and put the ROM on it and flash
Click to expand...
Click to collapse
Who are you speaking to? lol
PLEASE HELP ME!! My prime is stock in the first screen!!
Please i need help!! my transformer prime stock in the first screen after i use the ROM Manager to go to CWM...
Wasatronic said:
Please i need help!! my transformer prime stock in the first screen after i use the ROM Manager to go to CWM...
Click to expand...
Click to collapse
I blame rom manager for half of these bricks. It is letting people flash an ICS version of Cwm regardless of what bootloader they are on. Someone should speak to them.
Your tegra logo is in the bottom right meaning you are on the jellybean bootloader. You have flashed a ICS recovery on there and unless you have NVFlash backups or can get into fastboot then you are hard bricked.
Hi everyone, I think I've done a bad damage on my TF201. I was an happy user of [ROM]BAKED TF201 bb-8 (3-16-2013) with TWRP 2.5.0 as recovery, when today I decide to flash the [ROM][Apr 4][JB 4.2.1] AndroWook Prime Hairy Bean v2.11. Doing that I did flash before this file JB.4.2.1.Bootloader.and.partitions.zip. ROM was doing ok, so I decide than to flash via Terminal the TWRP 2.5.0, as the previous one was push me back with the 2.4.4.0. Unfortunately after booting into recovery is asking me the password that I don't remember, and now I am not able anymore to flash any ROM or restore any backup as the TWRP won't show me anything as is keep me asking for a password and when I ask to reboot is telling me that nor OS or SuperUser is available.... Is any solution for this mess that I've done?
Many thanks for the support, I am really desperate now!
EDIT: ok I did manage to resume the ROM, but is any way to recover the passwordto TWRP 2.5.0 recovery?
paura01 said:
Hi everyone, I think I've done a bad damage on my TF201. I was an happy user of [ROM]BAKED TF201 bb-8 (3-16-2013) with TWRP 2.5.0 as recovery, when today I decide to flash the [ROM][Apr 4][JB 4.2.1] AndroWook Prime Hairy Bean v2.11. Doing that I did flash before this file JB.4.2.1.Bootloader.and.partitions.zip. ROM was doing ok, so I decide than to flash via Terminal the TWRP 2.5.0, as the previous one was push me back with the 2.4.4.0. Unfortunately after booting into recovery is asking me the password that I don't remember, and now I am not able anymore to flash any ROM or restore any backup as the TWRP won't show me anything as is keep me asking for a password and when I ask to reboot is telling me that nor OS or SuperUser is available.... Is any solution for this mess that I've done?
Many thanks for the support, I am really desperate now!
EDIT: ok I did manage to resume the ROM, but is any way to recover the passwordto TWRP 2.5.0 recovery?
Click to expand...
Click to collapse
Go and read the disclaimer that is in big writing at the beginning of the hairy bean thread and then come back here and say what you have done wrong
not sure where you're talking about....
EDIT:
I am facing with this issue you posted here http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
after rebooting the tablet goes straight into recovery, still 2.5.0. The only way to load the rom is reboot the device via adb then with Volume - selecting androd icon and load it.
Quick note: after rebooting via adb I've got a message on top left position of the tablet as follow:
Key driver not found..Booting OS
Android cardhu-user boot loader <1.00 e> released by "WW_epad-10.6.1.2.8-20130225" A03
paura01 said:
not sure where you're talking about....
EDIT:
I am facing with this issue you posted here http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
after rebooting the tablet goes straight into recovery, still 2.5.0. The only way to load the rom is reboot the device via adb then with Volume - selecting androd icon and load it.
Quick note: after rebooting via adb I've got a message on top left position of the tablet as follow:
Key driver not found..Booting OS
Android cardhu-user boot loader <1.00 e> released by "WW_epad-10.6.1.2.8-20130225" A03
Click to expand...
Click to collapse
I'm talking about reading this section.
"READ EVERYTHING CAREFULLY. THIS IS NOT JUST FLASHING ANOTHER ROM
This Rom has been tested by many people but if you do not follow the instructions correctly or then go on to flash an incompatible TWRP you can brick yourself.
DO NOT INSTALL ANY OTHER RECOVERY WHILE USING THE NEW 4.2.1 BOOTLOADER, THEY ARE NOT COMPATIBLE AT THE MOMENT, THE ONE BUILT IN IS MODDED. USE THE DOWNGRADE ZIP TO TAKE YOU BACK TO 4.1.1 BOOTLOADER AND RECOVERY IF YOU NEED IT."
You ignored it and installed 2.5.0 even tho I had posted not to and now you are half bricked.
The post you just linked to is your only chance to recover. If one of the ways does not fix you in that post or you do not have nvflash backups there is nothing I can do sorry.
ok so if flashing either via Terminal or fastboot, would not replace the current TWRP 2.5.0, I am half screw then....
No I never manage to have the nvflash backups, the only backup I have is the one related to the previous ROM with TWRP 2.5.0 image, but of course I am not able to see it now.
Stupid question as I am not aware about it: is the nvflash backups related to a specific hardware or can it be use to any TF201 tablets?
Thanks for your tips
paura01 said:
ok so if flashing either via Terminal or fastboot, would not replace the current TWRP 2.5.0, I am half screw then....
No I never manage to have the nvflash backups, the only backup I have is the one related to the previous ROM with TWRP 2.5.0 image, but of course I am not able to see it now.
Stupid question as I am not aware about it: is the nvflash backups related to a specific hardware or can it be use to any TF201 tablets?
Thanks for your tips
Click to expand...
Click to collapse
Nvflash backups can only be used on the machine they were created on.
and of course do it now wouldn't be possible....
appreciate your help anyway, if you have maybe another idea is more than welcome!
would be possible in recovery with adb copy the ROM into the tablet and flash it?
paura01 said:
would be possible in recovery with adb copy the ROM into the tablet and flash it?
Click to expand...
Click to collapse
That isn't possible because you have the wrong TWRP on there for the bootloader and it can't mount any of the partitions it needs.
flumpster said:
That isn't possible because you have the wrong TWRP on there for the bootloader and it can't mount any of the partitions it needs.
Click to expand...
Click to collapse
... Too good to be true. I think I have to hope for a new TWRP or Hair release which may fix this half brick.
Thank you
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
flumpster said:
That isn't possible because you have the wrong TWRP on there for the bootloader and it can't mount any of the partitions it needs.
Click to expand...
Click to collapse
... Too good to be true. I think I have to hope for a new TWRP or Hair release which may fix this half brick.
Thank you
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
apparently you and I have the same problem: http://forum.xda-developers.com/showthread.php?t=2245136
any more idea for us?
I think we just need to hope for a new TWRP release and see if it would be flashable, otherwise stay in this half brick condition till new update
Hello guys, it's me again.
This time i wanted to try out flashing boot.img's. Something went horribly wrong, and whenever i try to reboot my device, it ends up in recovery mode (TWRP for Rockchip's).
Also, when i do click reboot, it says "No OS Installed! Are you sure you wish to reboot?". I swipe, then it shows something about installing SU.
But when it does, it just shows my manufacturer (meanIT)'s logo and goes directly into recovery.
I have just two questions:
Is it repairable?
Is my OS really deleted or is it just softbricked or something?
I'm starting to feel desperate, cause i'm not a pro at flashing, i could be called semi-noob.
Additional info:
Device: meanIT M754 Promise 7", Rockchip 3026.
Bootloader access: No.
Bootloader unlocked: No.
Recovery: TWRP v2.7.0.0 modified for Rockchip's.
Recovery access: Yes.
Thanks for support.
Did you make a nandroid backup before attempting to install a new kernel? If not...shame. LoL If so, just restore that and reboot. If you didn't, then you should be able to adb push a rom zip to your phone via adb in recovery - or if you have an SD card then put it on there. Worst case scenario, you can just the flash tool to restore your phone if you can find the stock files.
es0tericcha0s said:
Did you make a nandroid backup before attempting to install a new kernel? If not...shame. LoL If so, just restore that and reboot. If you didn't, then you should be able to adb push a rom zip to your phone via adb in recovery - or if you have an SD card then put it on there. Worst case scenario, you can just the flash tool to restore your phone if you can find the stock files.
Click to expand...
Click to collapse
Nope, i didn't backup, unfortunately. I'll try the adb method. Thanks!
+1 Thanks
Always always always make a backup whenever messing with kernels or major changes to the /system. You probably figured that out by now, but can't be stressed enough. Good luck.
I found a rom and tried to flash it.
When it flashed, i rebooted the tablet.
But...now it's stuck at meanIT boot logo screen. (not bootloop, it's just that boot logo shows up and disappears in snow).
I can't even access recovery anymore. I try to push the Power button for 5 secs to shut it down, but it powers up to the boot logo again. And so again and again, and again. Like a...bootlogoloop? lol.
Something went horribly wrong. :I
Update: It finally dies after the battery is drained.
Can anyone tell me what to do? (e.g. buy a new tablet, some repair advice, anything?) I'd be thankful. A lot.
Seriously? No one?
Are you able to get into fastboot? If so, you could try flashing your custom recovery image again.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Theonew said:
Are you able to get into fastboot? If so, you could try flashing your custom recovery image again.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope, but i played around with the buttons, trying every combination. Turns out i can force shutdown the bootloop and enter recovery mode by holding Power and VolUp while the bootloop. The only problem is, roms hard to find, man. But i found one which might seem to work so i'll try.
Sorry for bothering guys. I'm kind of a noob here, so excuse me if i turn out stupid.
No hope so far
So basically i tried everything except flashing a rkimage from sd card (don't have one big enough for the firmware).
Because i just found out there is a way to install Windows 8 on good working tablets, but i don't have money by the hand at the moment to buy a new one. I seriously don't know what to do anymore. I think it's either softbrick or just recovery loop.
Q&A for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
hhzznn said:
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
Click to expand...
Click to collapse
Hello there,
If not using the "adbsetup" drivers or the ones off the ASUS website (sorry, couldn't find the ASUS drivers when I looked ), use one of the above. If using one and still not connecting, try the other option.
Also, check your USB ports to make sure you are not connecting via a USB 3.x standard. Android (or at least some Android devices) don't like those.
If all else fails, you may need a Linux build
Hope this provides a head start.
Sent from my LG-D520 using XDA Free mobile app
help me please
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
hhzznn said:
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
Click to expand...
Click to collapse
Looks you got a little further... :good:
From what I remember when I followed the guide, there was no feedback (nothing on the screen, and tablet remains black) on when you issue the unlock commands - which by the way, are:
Code:
fastboot oem unlock61646
fastboot oem unlockD696E
Then, reboot the bootloader and install CWM (first line may be substituted with rebooting into fastboot by hand):
Code:
fastboot reboot-bootloader
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
You shouldn't get a write-protect error this time around. Hope this helps.
By the way, your SKU is WW version, right? If not, my ROM may not help you (without going the long way around of instead of flashing the ROM, copying the odex files back into /system/app using CWM's ADB push command). Just a warning. If you are not WW, and insist on flashing anyway, I would highly recommend a nandroid backup (and probably copied) to MicroSD to protect your original (broken) ROM.
help me
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
hhzznn said:
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
Click to expand...
Click to collapse
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
the code:fastboot unlock oem61646 worked but fastboot oemD696E not working
in stock recovery i cant install rom.zip
and in fastboot when install recovery cwm answer bootloader lock
any offer for me?
---------- Post added at 09:14 AM ---------- Previous post was at 09:07 AM ----------
**you may need a Linux build **
i have a linux base ,, may you help me??
hhzznn said:
**you may need a Linux build **
i have a linux base ,, may you help me??
Click to expand...
Click to collapse
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
i have ubuntu....what should i do?
hhzznn said:
i have ubuntu....what should i do?
Click to expand...
Click to collapse
In a terminal...
apt-get install android-tools-fastboot
...would be a good start. You may need to register the device vendor in your configuration, which I can research later if...
fastboot devices
...lists nothing. Hope this helps.
Sent from my LG-D520 using XDA Free mobile app
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Syncline said:
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Click to expand...
Click to collapse
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
joel.maxuel said:
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
Click to expand...
Click to collapse
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Syncline said:
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Click to expand...
Click to collapse
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
joel.maxuel said:
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
Click to expand...
Click to collapse
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Syncline said:
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Click to expand...
Click to collapse
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
joel.maxuel said:
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
No I wasn't encrypted before but from what I read it seems to involve a failure to mount the DATA partition correctly, and the Android OS erroneously assumes it's encrypted. I'm not overly concerned about setting up apps by hand, I do have a titanium backup of my apps and data. As I'm still at work, I can't do too much playing around on my tablet. I don't have access to my personal computer that has all my tools like adb, fastboot, etc. until the work day is done. I've said it a couple of times, but I truly appreciate the assistance that you've provided.
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Syncline said:
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Click to expand...
Click to collapse
That's an interesting side effect...never had that happen before.
You can try it, and let me know. Hopefully your CWM is still kicking around, or else you will have to reinstall via fastboot. Or alternatively, just re-root normally (like with Kingo).
By the way, before you do that, does /system/xbin/su exist? Or what you could answer, is you could download Voodoo OTA RootKeeper and report back which values are not checked off. I think SuperSU update.zip places the su binary, nothing else. But we shall see.
Sorry Joel, I didn't see your reply before I flashed the SuperSU zip but it did work, my tablet is rooted again.
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