Related
Hey folks,
I have a couple of question before rooting, i was going to use regaw_leinad 2.1 guide unless anyone has a better suggestion ?
1. By rooting my phone am I removing the standard ROM or just making it that I can edit it?
2. How does one install a new ROM for example the ALOYSIUS 2.1 looks great but i haven't a clue what to do?
Any help is much appreciated
thatenglishguy said:
I have a couple of question before rooting, i was going to use regaw_leinad 2.1 guide unless anyone has a better suggestion ?
Click to expand...
Click to collapse
Yeah, that's what I do.
thatenglishguy said:
1. By rooting my phone am I removing the standard ROM or just making it that I can edit it?
Click to expand...
Click to collapse
There are 2 parts to what you are doing. You are gaining root access, and then you are using that access the write a new recovery image to your phone. You may keep the standard ROM.
thatenglishguy said:
2. How does one install a new ROM for example the ALOYSIUS 2.1 looks great but i haven't a clue what to do?
Click to expand...
Click to collapse
You install new ROMs using the recovery image you installed while rooting your phone. Copy the .zip file(s) for the ROM you want to flash to the root directory of your sdcard. Boot to recovery by holding the HOME key while you press the power button. In recovery, you have the option to backup your existing ROM and to install a new one.
Thanks
Awesome, thank you v much indeed.
I have rooted my phone with Regaw's instructions, and it was very straight-forward.
1.) When you root your phone, you have a special recovery image that you can boot the phone into, and basically back up/restore your phone in case you decide to flash different roms and didn't like it, or you screwed up somewhere along the way. You can toggle the usb function, meaning you can use a terminal emulator (command prompt for windows) and move files between your pc and the phone while in recovery. You can theme your phone, can remove unwanted apps, use apps from the market that require you to have root access.
The simplest reason; to have full control of your phone.
2.) When you aquire root on your phone and able to boot into recovery and such, you can take the zip file that the rom was created in, and transfer it to the root of your sd card. Then you can either A) Open the command prompt, type in adb shell then type in reboot recovery while the phone is plugged in with the pc. The phone will reboot into recovery. B) Just power off the phone completely, then press and hold the home key and turn the phone on until you get to the recovery screen. From there you will need to backup your phone if you haven't already. Select backup/restore, then select nand backup. It will take a few minutes for this process to complete. When finished, you can go back to the main screen, and select wipe. Then select wipe data/factory reset. Press the home key to confirm. Go back and select wipe Dalvik-cache.
When done, go back to the main screen and select flash zip from sdcard. Scroll to the rom that you put in and select it. It should take a couple minutes to flash the new rom on your phone. When it's finished, you need to reboot your phone. The reboot process will take about 5-10 minutes depending on the type of rom that you flashed.
A few tips:
*Once you root, you have voided your warranty for the phone. But have no fear! Make sure you save your sdcard to your PC and run the RUU before bringing the phone for service if you need to. When service is done, you may transfer your sdcard contents from the pc back to your phone, do a quick root, and you are good to go.
*When wiping, your phone will be factory reset, meaning you have to sign into google again, redownload all your apps from the market if you have any.
*If you do like the rom of your choice, try to tweak it out the best you can, then do a nandroid (backup your phone) just in case you flash another rom. If you flash a second or third rom or whatever and didnt like it, you may do a restore on your phone, and all your info will be saved from the last nandroid you made. Be careful on how many nandroid you do. It takes up space on your sdcard. You may rename your nandroids, and remove the ones you don't want.
*The battery may get hot when flashing roms. This is normal, just try not to over do it.
*This Hero CDMA forum is now your best friend. Read and search, read and search before posting a question. Not that we don't mind answering questions, but if it has been asked 50 times, some people will give you snarky comments.
Good luck!
thanks , one more thing
Very helpful and I have successfully rooted my Hero !
Now regarding the new ROM I have downloaded the Zip file do I just copy the whole thing onto my phones sd card? If so where into the Nandroid folder?
Or do I run it using CMD from my laptop and if so know of any guides on how?
Thanks again, muchly appreciated
MB
Easiest way is you mount your phone to pc via usb, and just drop the zip file onto the root of your sdcard. Do not place the zip file anywhere else, or in any folder, just in the sdcard itself. Remount the phone, reboot into recovery, and select flash zip. Your rom should be in there to flash.
A wise man once said, "You've taken your first step into a larger world."
So happy you guys were nice with helping him. I'm finally making my switch to Android (in 3.5hrs). I can't wait to get home and root and figure it all out. Seems a TAD more difficult than it was with WinMo. There's SOOOOOO much info here, it's difficult to figure out WHERE start. But this thread helped at least figure out WHICH guide to follow initially.
**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!
We've been trying everything to get in but no such luck. I've been reading around and come to the conclusion that we won't be able to. Then I thought I'd return to stock from recovery but can't even get into that. Will the phone remain that way forever or is there someway to reset it?
Thrillwaters said:
We've been trying everything to get in but no such luck. I've been reading around and come to the conclusion that we won't be able to. Then I thought I'd return to stock from recovery but can't even get into that. Will the phone remain that way forever or is there someway to reset it?
Click to expand...
Click to collapse
first I am sorry for your loss.
if you want to bypass screen lock and have a working recovery,you can remove the file named"gesture.key" and after rebooting into system every password you inter , unlocks the phone.
if you have TWRP ,first go to recovery,mount data partition : go to mount section and check data.
then return to main menu and go to advanced section and choose file manager .
then go to the /data/system
find a file named "gesture.key" and delete that file by long pressing on it and choose delete.
now reboot the phone into system and in lock screen enter what you want ,no matter the phone will unlock.
if you have philz touch recovery or CWM .
FIRST download "aroma file manager" from here.http://d-h.st/iqn
then place it to your sdcard.
reboot to recovery ,mount data partition,and then flash aroma file manager you've downloaded above.
then just go to /data/system and remove "gesture.key" and it's done.
press thanks if you find this helpfull.
mrp1375 said:
first I am sorry for your loss.
if you want to bypass screen lock and have a working recovery,you can remove the file named"gesture.key" and after rebooting into system every password you inter , unlocks the phone.
if you have TWRP ,first go to recovery,mount data partition : go to mount section and check data.
then return to main menu and go to advanced section and choose file manager .
then go to the /data/system
find a file named "gesture.key" and delete that file by long pressing on it and choose delete.
now reboot the phone into system and in lock screen enter what you want ,no matter the phone will unlock.
if you have philz touch recovery or CWM .
FIRST download "aroma file manager" from here.http://d-h.st/iqn
then place it to your sdcard.
reboot to recovery ,mount data partition,and then flash aroma file manager you've downloaded above.
then just go to /data/system and remove "gesture.key" and it's done.
press thanks if you find this helpfull.
Click to expand...
Click to collapse
Thanks for the reply, but I should've made it clear. I don't think the phone has a recovery installed. I've tried all the combinations (power plus volume up etc.) but no luck. If I hold the power plus volume up it vibrates three times and that's it.
Thrillwaters said:
Thanks for the reply, but I should've made it clear. I don't think the phone has a recovery installed. I've tried all the combinations (power plus volume up etc.) but no luck. If I hold the power plus volume up it vibrates three times and that's it.
Click to expand...
Click to collapse
so if the phone has no recovery installed,but the bootloader is unlocked ,you can flash a custum kernel with built in recovery like Zombie kernel and then do the rest things.
but if the bootloader is locked.you simply can't do anything.
but there is a question here: what you looking for?
a)you just want to unlock the phone and you don't need the data that stored in it.
b)you want the phone to be unlocked ,without touching the data.
Yeah I have no idea if the boatloader is unlocked. I assume not.
At first we wanted to get in and see if he had any pictures, but accept that it might not be possible. Just seems a shame to have a brick lying around, so in that case I wanted to know if it's possible to wipe it and start again. Thanks for the help.
Thrillwaters said:
Yeah I have no idea if the boatloader is unlocked. I assume not.
At first we wanted to get in and see if he had any pictures, but accept that it might not be possible. Just seems a shame to have a brick lying around, so in that case I wanted to know if it's possible to wipe it and start again. Thanks for the help.
Click to expand...
Click to collapse
I sorry for your loss ,god bless him and gives patient to you
if u dont want to save some data like sms,mms,contacts,emails and so on u can simply install last flash tools on your computer, and then download any FTF firmware and flash it on the phone with check clear data box, or just tik the clear data box, this method would not wipe internal/external memory and u can save pictures,movies and all of files in internal/external SD (remember to not wipe internal SD) and u can use the phone
i also sorry for my bad english
jing000l said:
I sorry for your loss ,god bless him and gives patient to you
if u dont want to save some data like sms,mms,contacts,emails and so on u can simply install last flash tools on your computer, and then download any FTF firmware and flash it on the phone with check clear data box, or just tik the clear data box, this method would not wipe internal/external memory and u can save pictures,movies and all of files in internal/external SD (remember to not wipe internal SD) and u can use the phone
i also sorry for my bad english
Click to expand...
Click to collapse
Thanks for the wishes.
Does the flashtools work with mac? Tried to find a mac version but couldn't.
OK problem solved! Thanks everyone. We managed to figure out the pin. He had them all written down. Silly him.
Hello.
I'm having issues TWRP backups. Maybe I was undone system. I need a friend using the honor 7 PLK-L01 system backup of your phone by then compressed .zip TWRP.roi nk.len up for me to use. My machine is now no longer on the operating system.
*Help me.
thank you
There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.
memht said:
There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.
Click to expand...
Click to collapse
Thank.
multi tool can use the phone while I was hanging not. and restore them in any way.
memht said:
There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.
Click to expand...
Click to collapse
after restore I saw this line
"MD5 failed to match on ... / ... twrp / backups /............./.........../ system.ext4.win001"
do not know why?
hotboymen2026 said:
after restore I saw this line
"MD5 failed to match on ... / ... twrp / backups /............./.........../ system.ext4.win001"
do not know why?
Click to expand...
Click to collapse
I don't know actually but md5 errors are usually harmless. But if your recovery is working, just do fresh installation.
memht said:
I don't know actually but md5 errors are usually harmless. But if your recovery is working, just do fresh installation.
Click to expand...
Click to collapse
Do not really undersand. I've manually restore your backup files, but only running to 99%. and restore fail.
Errors are displayed MD5 "system.ext4.win001"
hotboymen2026 said:
Do not really undersand. I've manually restore your backup files, but only running to 99%. and restore fail.
Errors are displayed MD5 "system.ext4.win001"
Click to expand...
Click to collapse
Actually I am really confused.. What is your phone's condition right now? And what do you want to do?
memht said:
Actually I am really confused.. What is your phone's condition right now? And what do you want to do?
Click to expand...
Click to collapse
Status phone rom I'm wrong. logo only lead to hang on is TWRP, connect PC and Fastboot. but when I rom stock (PLK-L01 C432B270) is successful but unable to reboot the operating system. H7 is due to the security, it's hard to be rescued. I also put it into the service center (not the local machine), they also confused with my H7. I need to find ways to revive it, no matter how well!
hi,
I bought a new Huawei P10 lite phone, unlocked the bootloader, installed TWRP and with this I installed SuperSU via microSD card.
Everything worked fine, until now. Now I want to backup my current modified stock ROM, but TWRP failes.
I got the problem very fast: TWRP can read all files and folders on the microSD car, but not in the internal storage folder.
The file structure is like the following:
acct
boot
cache
config
data
...
etc
external_sd <-- the microSD card
mnt
...
sbin
sdcard
storage
...
Click to expand...
Click to collapse
Everything can be read by TWRP, except the sdcard folder.
Here he only shows strange names (crypted I guess):
something like:
2h8P9lGY8I1A884LMsBjaA
2u+nb0LdBNopRSa5LehsvB
75aTrCvYkWG+R+lrcRz6WA
DcwYkwSKokq8Rm5lYc4YYC
...
Click to expand...
Click to collapse
This strange folders occure within TWRP itself and also if I mount the storage to the computer via TWRP.
I also can not modify, delete or add anything in this cryted folder.
So what am I doing wrong? Why is this crypted and can not be read?
During my research I found this post on reddit with the same problem. But the solution is not clear to me and also not working.
Thanks for any help
greetings
Christopher
PS.: Here some specific information about the phone:
brand new Huawei P10 lite
model WAS-LX1A
build nr. WAS-LX1AC432B102
no updates avaible, checked twice
EMUI 5.1 with Android 7.0
TWRP v3.1.0-2 from here (named "TWRP_P10_Lite_Beta.img")
Hey
It's because your files are encrypted due to forceecnryption and dm-varity in the kernel you can try formating the data to see if it removes the encryption from the data.
My infos may not be correct you can read more about dm-varity and forceecnryption in the internet
aburezk said:
Hey
It's because your files are encrypted due to forceecnryption and dm-varity in the kernel you can try formating the data to see if it removes the encryption from the data.
My infos may not be correct you can read more about dm-varity and forceecnryption in the internet
Click to expand...
Click to collapse
Ok, thanks a lot. This was helful so far.
From what I read, I now must flash a new "boot.img" in order to disable force encryption. But where do I get such a file for my Huawei P10 lite (WAS-LX1A)? I did not found one. Maybe the phone is too new? Or am I just blind?
greetings
christopher2007 said:
Ok, thanks a lot. This was helful so far.
From what I read, I now must flash a new "boot.img" in order to disable force encryption. But where do I get such a file for my Huawei P10 lite (WAS-LX1A)? I did not found one. Maybe the phone is too new? Or am I just blind?
greetings
Click to expand...
Click to collapse
you can't find it anywhere
aburezk said:
you can't find it anywhere
Click to expand...
Click to collapse
Ok, so too new ... damn. That is very bad.
christopher2007 said:
Ok, so too new ... damn. That is very bad.
Click to expand...
Click to collapse
I managed to disable force encryption on my device
Download this and flash it
Backup your data and wipe data from twrp
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
I tryed no-verity-opt-encrypt-6.0.zip but now do not start anymore... I have restore boot and system but none... what can I do? I think i will sell this p10 lite...
simona70 said:
I tryed no-verity-opt-encrypt-6.0.zip but now do not start anymore... I have restore boot and system but none... what can I do? I think i will sell this p10 lite...
Click to expand...
Click to collapse
i had the same issue by using no-verity-opt-encrypt-6.0.zip. The phone was brick after that.
Do you know your Build of your Phone ? If yes you can download the right Update.app from Huawei and extract the BOOT.IMG, RECOVERY.IMG and the SYSTEM.IMG (Maybe CUST.IMG) and restore it in the fastboot Mode. After that it started again to the UI.
If you dont know the Build of your Phone there will be some Fastboot oem commands to get it (i dont have them in my mind right now).
I flashed the ZIPs in TWRP after that with an external SD card witch arent crypted names...
ChipCollector said:
i had the same issue by using no-verity-opt-encrypt-6.0.zip. The phone was brick after that.
Do you know your Build of your Phone ? If yes you can download the right Update.app from Huawei and extract the BOOT.IMG, RECOVERY.IMG and the SYSTEM.IMG (Maybe CUST.IMG) and restore it in the fastboot Mode. After that it started again to the UI.
If you dont know the Build of your Phone there will be some Fastboot oem commands to get it (i dont have them in my mind right now).
I flashed the ZIPs in TWRP after that with an external SD card witch arent crypted names...
Click to expand...
Click to collapse
I solved using "update_data_full_public.zip" and clearing /data, after restoring previuos boot.img and system.img .
My phone was WAS-LX1AC432B102 4gb EMUI5.1 Android 7.0. I had bricked before and the only way to unbrick was to use "Warsaw-L21_C432B182_EU_SERVICE_androidhost.ru"
I do not trust to install data into a phone i can't backup and restore with TWRP... there is another way to make /data not crypted?
Exist the hope one day TWRP read also crypted /data or it is better search another phone?
ChipCollector said:
i had the same issue by using no-verity-opt-encrypt-6.0.zip. The phone was brick after that.
Do you know your Build of your Phone ? If yes you can download the right Update.app from Huawei and extract the BOOT.IMG, RECOVERY.IMG and the SYSTEM.IMG (Maybe CUST.IMG) and restore it in the fastboot Mode. After that it started again to the UI.
If you dont know the Build of your Phone there will be some Fastboot oem commands to get it (i dont have them in my mind right now).
I flashed the ZIPs in TWRP after that with an external SD card witch arent crypted names...
Click to expand...
Click to collapse
Hey, I am having the exact same problem, my phone is soft bricked after no-verity-opt-encrypt-6.0.zip. (https://forum.xda-developers.com/p10/help/stuck-device-booting-flashing-rom-t3713503).
I know the build of my phone, and I downloaded the update.app and extracted it to boot.img, recovery.img, system.img, but how exactly can I restore it in the fastboot mode. What commands?
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------
Anymore I think P10lite is a lost cause. I sell to my mother. I bought a xiaomi redmi note 4 global. Never again a Huawei. What a disappointment.
You'll sale your phone to your? Mother? To your mother?
Anyway the same story is on redmi note and all xiaomi
Phones
All the Chinese are difficult to modify.
I was have all Nexus thru 2011 very easy phones but the Chinese... My...
I have a doubt, I have bundled it when trying to install root on my device and I ended up in bootloop what I did was install a (official) rom which when entering the internal files, the folders were with strange names appear, so you recommend removing the credentials (decrypt), to be able to install root? My Device is Xiaomi mi A2
Bro did you find a solution..I am having same problem help
Had my phone bricked two days ago after a failed Motorola system update. Decided do ditch it and go with LineageOS, wich I got working after a few failed install attempts. When I tried to acess my internal storage, I had only those randomly named folders. Deleted them all, but couldn´t write to my storage after. Even tried a camera app, and it said that couldn´t work without a sdcard.
SOLUTION: boot recovery on TWRP > Wipe > Advanced Wipe> select ONLY internal storage > swipe to wipe :good:
Rebooted after internal storage wipe and everything is fine now. It seems all the install attempts made some sort of mess.
chimeralounge said:
Had my phone bricked two days ago after a failed Motorola system update. Decided do ditch it and go with LineageOS, wich I got working after a few failed install attempts. When I tried to acess my internal storage, I had only those randomly named folders. Deleted them all, but couldn´t write to my storage after. Even tried a camera app, and it said that couldn´t work without a sdcard.
SOLUTION: boot recovery on TWRP > Wipe > Advanced Wipe> select ONLY internal storage > swipe to wipe :good:
Rebooted after internal storage wipe and everything is fine now. It seems all the install attempts made some sort of mess.
Click to expand...
Click to collapse
Legend. This fixed the same issue we were facing on the t510 Samsung tablet. Saved us a lot of trouble. Thanks for this.
memz180 said:
Legend. This fixed the same issue we were facing on the t510 Samsung tablet. Saved us a lot of trouble. Thanks for this.
Click to expand...
Click to collapse
-----------
Cool, glad to help! In fact, this issue happened to me once again a few weeks back, when LegacyOS updated. I had this "f*** here we go again" moment, but before wiping, I decided to use TWRP > Advanced > Fix Content. Not only I got the system working again, but *all my data was intact*. System updates are messing file tables, apparently.
I want to marry TWRP.
chimeralounge said:
Had my phone bricked two days ago after a failed Motorola system update. Decided do ditch it and go with LineageOS, wich I got working after a few failed install attempts. When I tried to acess my internal storage, I had only those randomly named folders. Deleted them all, but couldn´t write to my storage after. Even tried a camera app, and it said that couldn´t work without a sdcard.
SOLUTION: boot recovery on TWRP > Wipe > Advanced Wipe> select ONLY internal storage > swipe to wipe :good:
Rebooted after internal storage wipe and everything is fine now. It seems all the install attempts made some sort of mess.
Click to expand...
Click to collapse
God bless you! i've struggle with this s]+t for hours!
what worked for me is installing siankatabg-twrp , now i can see names fine
after that i changed back to official version (which was missy before) and still fine !!!!!!!!
then installed orange fox (which was missy before) and still fine !!!!!!!!
WTH !!!!!!!!!!!!
so i think best shot (if u dont have siankatabg-twrp) is installing codeworkx (Lineage recovery) make sure all good then go back to ur favorite.
lemme know if its works