Related
After updating my e700h to stock 5.1.1 i had rooted it successfully using KingRoot
Now I need to flash xposed framework zip file that needs a custom recovery
I tried TWRP for kitkat and it didnt work
I even tried a lolipop compatible CWM for E5 and it was very funny and useless
So can anyone compile any custom recovery for E7 running 5.1.1
Here's the img file of the stock recovery
mega.nz/#!ocoThQ7A
Thanks
hashiesh said:
After updating my e700h to stock 5.1.1 i had rooted it successfully using KingRoot
Now I need to flash xposed framework zip file that needs a custom recovery
I tried TWRP for kitkat and it didnt work
I even tried a lolipop compatible CWM for E5 and it was very funny and useless
So can anyone compile any custom recovery for E7 running 5.1.1
Here's the img file of the stock recovery
mega.nz/#!ocoThQ7A
Thanks
Click to expand...
Click to collapse
It will be available soon and could you upload boot and recovery to google drive or devhost.
nepalbiraj said:
It will be available soon and could you upload boot and recovery to google drive or devhost.
Click to expand...
Click to collapse
Uploaded, Check them out & help us giving custom recovery
https://drive.google.com/folder/d/0B_8xPQyhA4WxRHRkNWFZYnZUblU/edit
nepalbiraj said:
It will be available soon and could you upload boot and recovery to google drive or devhost.
Click to expand...
Click to collapse
Thanks a lot ... I tried to reply to your post but unforunately I'm less than 10 posts old
Here are the files
https //) drive.google.com/a/hashiesh.com/folderview?id=0BxgiSTfvJheVYm04MUo5NmdBcDg&usp=sharing
Thanks a lot
Me too. Please make cusTom recovery for e7 running 5.1.1
Waiting for the recovery guys please help!
i tried the custom recovery in this link
http://forum.xda-developers.com/gal...ry-twrp-touch-recovery-sm-e700-t3267563/page5
but after flashing through flashify i got stuck on logo...
my device is E700H running 5.1.1
what should i do to make twrp work?
crimson35th said:
i tried the custom recovery in this link
http://forum.xda-developers.com/gal...ry-twrp-touch-recovery-sm-e700-t3267563/page5
but after flashing through flashify i got stuck on logo...
my device is E700H running 5.1.1
what should i do to make twrp work?
Click to expand...
Click to collapse
Try the lollipop twrp it has been built last night heres the thread http://forum.xda-developers.com/showthread.php?t=3267563
Press thanks if it works for you
---------- Post added at 12:14 PM ---------- Previous post was at 12:08 PM ----------
hashiesh said:
After updating my e700h to stock 5.1.1 i had rooted it successfully using KingRoot
Now I need to flash xposed framework zip file that needs a custom recovery
I tried TWRP for kitkat and it didnt work
I even tried a lolipop compatible CWM for E5 and it was very funny and useless
So can anyone compile any custom recovery for E7 running 5.1.1
Here's the img file of the stock recovery
mega.nz/#!ocoThQ7A
Thanks
Click to expand...
Click to collapse
This recovery will not be funny I swear?here it is https://www.androidfilehost.com/?fid=24369303960682868 and the thread link http://forum.xda-developers.com/gal...recovery-twrp-touch-recovery-sm-e700-t3267563
@duonglam @rahulsajilekha @crimson35th
Press thanks if it works for you.
need help plzz
nepalbiraj said:
Try the lollipop twrp it has been built last night heres the thread http://forum.xda-developers.com/showthread.php?t=3267563
Press thanks if it works for you
---------- Post added at 12:14 PM ---------- Previous post was at 12:08 PM ----------
This recovery will not be funny I swearhere it is https://www.androidfilehost.com/?fid=24369303960682868 and the thread link http://forum.xda-developers.com/gal...recovery-twrp-touch-recovery-sm-e700-t3267563
@duonglam @rahulsajilekha @crimson35th
Press thanks if it works for you.
Click to expand...
Click to collapse
how to falsh .img using odin ??
Hatem hesham said:
how to falsh .img using odin ??
Click to expand...
Click to collapse
You can flash it with the app Flashify or I have just uploaded the odin flashable zip . So that it can be flashed directly. I suggest to use the odin method.
it keeps rebooting into recovery
nepalbiraj said:
You can flash it with the app Flashify or I have just uploaded the odin flashable zip . So that it can be flashed directly. I suggest to use the odin method.
Click to expand...
Click to collapse
I installed the recovery using odin
whenever I want to restart my mob. it keeps rebooting to the recovery menu ??!!
what do i do?
this is my 2nd attempt
i reflashed my stock rom then flashed the cfroot and then the img file and i get recovery loop
which part did i do wrong? i did the reflashing of stock cuz i was expecting that it would go smoothly with freshly flashed stock rom
Hatem hesham said:
I installed the recovery using odin
whenever I want to restart my mob. it keeps rebooting to the recovery menu ??!!
Click to expand...
Click to collapse
It looks like a bug. Meanwhile you can try to flash stock recov again and do it all over again. This time flash the twrp with odin and uncheck auto reboot and reboot it manually.
And avoid rebootinh to recovery from the system. Boot to recovery only through the hardware buttons. (3 button combo) volume up+home button+power button.
And the restart button is volume down+power long press it.
---------- Post added at 01:55 AM ---------- Previous post was at 01:52 AM ----------
crimson35th said:
what do i do?
this is my 2nd attempt
i reflashed my stock rom then flashed the cfroot and then the img file and i get recovery loop
which part did i do wrong? i did the reflashing of stock cuz i was expecting that it would go smoothly with freshly flashed stock rom
Click to expand...
Click to collapse
Reflash twrp with auto reboot option off. Follow the instructions I gave to hashem.
it worked !!
nepalbiraj said:
It looks like a bug. Meanwhile you can try to flash stock recov again and do it all over again. This time flash the twrp with odin and uncheck auto reboot and reboot it manually.
And avoid rebootinh to recovery from the system. Boot to recovery only through the hardware buttons. (3 button combo) volume up+home button+power button.
And the restart button is volume down+power long press it.
---------- Post added at 01:55 AM ---------- Previous post was at 01:52 AM ----------
Reflash twrp with auto reboot option off. Follow the instructions I gave to hashem.
Click to expand...
Click to collapse
thanks very much for ur help ... it finally worked
it worked ... thanks a lot ! looking forward for more mods
Hatem hesham said:
thanks very much for ur help ... it finally worked
Click to expand...
Click to collapse
You are most welcome:victory::victory:
---------- Post added at 02:57 PM ---------- Previous post was at 02:53 PM ----------
crimson35th said:
it worked ... thanks a lot ! looking forward for more mods
Click to expand...
Click to collapse
You're welcome. Good to hear that it works for you Press thanks.
nepalbiraj said:
It looks like a bug. Meanwhile you can try to flash stock recov again and do it all over again. This time flash the twrp with odin and uncheck auto reboot and reboot it manually.
And avoid rebootinh to recovery from the system. Boot to recovery only through the hardware buttons. (3 button combo) volume up+home button+power button.
And the restart button is volume down+power long press it.
---------- Post added at 01:55 AM ---------- Previous post was at 01:52 AM ----------
Reflash twrp with auto reboot option off. Follow the instructions I gave to hashem.
Click to expand...
Click to collapse
Sorry for replying here, I'm still below 10 posts so I cant reply to your original post
First: no words are enough to thank you for you effort. It's working and really amazing. Thanks a lot
But I noticed something: when I tried to flash a rom that I have just created, I got an error message "This rom is for e73g while this device is e5lte" I dont know whether this is a problem in my device or it's recovery related
BTW I'm trying to create a deodexed debloated stock rom
Thanks again
hashiesh said:
Sorry for replying here, I'm still below 10 posts so I cant reply to your original post
First: no words are enough to thank you for you effort. It's working and really amazing. Thanks a lot
But I noticed something: when I tried to flash a rom that I have just created, I got an error message "This rom is for e73g while this device is e5lte" I dont know whether this is a problem in my device or it's recovery related
BTW I'm trying to create a deodexed debloated stock rom
Thanks again
Click to expand...
Click to collapse
Thanks for thanking me??hashiesh.
This is not the problem of the device nor recovery. In the META-INF folder in the Rom zip there is a file names UPDATERSCRIPT. Open it in notepad++ or any other tool and remove the first 3 lines.
There should be something written assert. It checks the device name.
So remove it and you are good to go.
Attach or share the updaterscript here so that we can look at it.
After success you can share the ROM in here.
nepalbiraj said:
Thanks for thanking mehashiesh.
This is not the problem of the device nor recovery. In the META-INF folder in the Rom zip there is a file names UPDATERSCRIPT. Open it in notepad++ or any other tool and remove the first 3 lines.
There should be something written assert. It checks the device name.
So remove it and you are good to go.
Attach or share the updaterscript here so that we can look at it.
After success you can share the ROM in here.
Click to expand...
Click to collapse
Thank you for your information, I found the 3 lines of "asserts" but i'm trying to set the assert to "e5lte" and will update you if it worked.
Sure I will upload it and it will be the first time to upload a rom after years of modifying stock and custom roms without even creating a flashable zip file
I'm planning to create 3 roms
1. Stock deoedexed deknoxed rooted with busybox
2. same as 1 but debloated (I consider all samsung apps to be bloatware)
3. Will try to replace samsung core apps with google ones from stock nexus gapps
so wish me luck and remember that all these are thanks to your TWRP
nepalbiraj said:
Thanks for thanking mehashiesh.
This is not the problem of the device nor recovery. In the META-INF folder in the Rom zip there is a file names UPDATERSCRIPT. Open it in notepad++ or any other tool and remove the first 3 lines.
There should be something written assert. It checks the device name.
So remove it and you are good to go.
Attach or share the updaterscript here so that we can look at it.
After success you can share the ROM in here.
Click to expand...
Click to collapse
please check this
http://forum.xda-developers.com/galaxy-e-series/development/dev-e700h-stock-deodexed-t3293510
Hi all,
I have a bit of an issue with the latest OTA update currently being pushed out and looking for help how best to proceed.
I have unlocked and rooted the phone previously and recovery is TWRP. My phone is encrypted.
When I accepted the updated the phone rebooted and showed the TWRP splash screen which flashes on and off endlessly. If I turn the phone off and on again it restarts fine but after a few seconds the update process starts again. I am currently stuck in this loop.
Any advice as to how I can get out of this without wiping my phone?
I am wondering if I could flash the standard recovery to remove TWRP if this would work. Could it and if so, where can i get the standard recovery image.
Thanks and sorry of this is already covered, I searched but couldn't find it.
For XT1575.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
If you want to update be on stock rom i.e. unrooted and no xposed,nothing added or removed from system and also flash stock recovery.
After successful update flash twrp.
So, if I want to install the lastest update it's enough to unroot, remove xposed and flash stock recovery? Or it's better to flash full stock through fastboot?
So I managed to find a link to the full image for my device (XT1572 so the above link wouldn't work to the best of my knowledge - but thanks anyway @Hitti2)
I flashed the standard recovery and rebooted which stopped the endless loop. The update still fails to install but I can live with that for now.
I'll investigate further what I need to do to get the update to take properly but for now I have a functioning phone which is a good start to the day.
Thanks all.
Sent from my XT1572 using Tapatalk
Final installment. Update installed and a good. For anyone who stumbles across this with a similar issue, here is what I had to do.
Flash stock boot and recovery images to remove root and TWRP.
Reboot and let the update install.
Reflashed TWRP and SuperSU (both of which are now newer versions)
Job done. Now I know for the next update [emoji6]
There is a whole thread dedicated to this update in general.
lafester said:
There is a whole thread dedicated to this update in general.
Click to expand...
Click to collapse
Maybe there is but as I stated in the OP, I couldn't find the right information at the time of posting. Maybe helpful would be to also link the thread as it may help others.
@lafester could you link thread please.
Sent from my XT1572 using Tapatalk
Boot image?
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
user7743 said:
Final installment. Update installed and a good. For anyone who stumbles across this with a similar issue, here is what I had to do.
Flash stock boot and recovery images to remove root and TWRP.
Reboot and let the update install.
Reflashed TWRP and SuperSU (both of which are now newer versions)
Job done. Now I know for the next update [emoji6]
Click to expand...
Click to collapse
nathlynn22 said:
@lafester could you link thread please.
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
This one possibly?
http://forum.xda-developers.com/moto-x-style/general/xt1575-february-2016-security-update-t3323126
---------- Post added at 10:42 PM ---------- Previous post was at 09:50 PM ----------
chuck-fu said:
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
Click to expand...
Click to collapse
Maybe this one?
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Though I am having issues too... stuck at Error! after trying to install update with (what I assume is) stock recovery and boot.
chuck-fu said:
Thanks for this info. I'm definitely still unable to install this update. I am stock, unrooted. I have flashed the stock recovery image, but not the boot image. Can you please point me to where i can find the stock boot image?
Click to expand...
Click to collapse
evandena said:
Maybe this one?
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Though I am having issues too... stuck at Error! after trying to install update with (what I assume is) stock recovery and boot.
Click to expand...
Click to collapse
@evandena not that one. That is for a different model, I needed the firmware for the XT1572.
@chuck-fu I found a post here on XDA with a list of download links for various versions. I will dig out the link shortly and post it when I have access to my PC.
I extracted but the recovery and boot image files from that package. What you need are the images as close to possible from what is currently installed on your phone.
Edit: Here is the link to the thread with many Moto X Style images... Hopefully this will help
[Firmware] Moto X Style/Pure Stock Software
Thanks so much for trying to help. I went ahead and flashed the boot and recovery files for my model. I did the Boot image first, no luck. then i did the recovery, and this time andy thought a bit longer before giving me the Error! message. And then instead of my phone doing an autoreboot, it was stuck on the dead Andy and I needed to do hold down the power button to get it to shut down.
Anyone have any additional thoughts?
user7743 said:
@evandena not that one. That is for a different model, I needed the firmware for the XT1572.
@chuck-fu I found a post here on XDA with a list of download links for various versions. I will dig out the link shortly and post it when I have access to my PC.
I extracted but the recovery and boot image files from that package. What you need are the images as close to possible from what is currently installed on your phone.
Edit: Here is the link to the thread with many Moto X Style images... Hopefully this will help
[Firmware] Moto X Style/Pure Stock Software
Click to expand...
Click to collapse
I was having same issue. I am stock, rooted, unlocked bootloader.
Currently using TWRP 3.0
In order to update with the new OTA you need to find a download of the .zip files and manually install it.
If you try to do OTA update it will just keep getting stuck in recovery. To get out of this just cache wipe and reboot.
This phone has never been able to take OTAs for some reason. I wish I understood why. I tried to leave the thing stock to keep things simple, but it wasn't to be... anyway...
Thanks for the advice. Any idea where to get a download of the .zip files (is it really more than one zip file, or was that a typo)? I tried searching, but can't seem to find the right things to search for.
Also, once i have the zip file(s):
1) Do I just install it via TWRP like any other zip file?
2) to get rid of the OTA prompt, do i wipe the cache and reboot before or after i install the update via the zip?
Many thanks!
InFamousD147 said:
I was having same issue. I am stock, rooted, unlocked bootloader.
Currently using TWRP 3.0
In order to update with the new OTA you need to find a download of the .zip files and manually install it.
If you try to do OTA update it will just keep getting stuck in recovery. To get out of this just cache wipe and reboot.
Click to expand...
Click to collapse
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Thanks for the info- what version do you have? I have the 1575 RETUS and can't find the system file. Is that basically flashing an entire ROM? Sorry, but i've flashed boot and recovery files before, as well as full ROMs but don't ever remember flashing a system file on its own.
Thanks!
Dunkel06 said:
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Click to expand...
Click to collapse
chuck-fu said:
Thanks for the info- what version do you have? I have the 1575 RETUS and can't find the system file. Is that basically flashing an entire ROM? Sorry, but i've flashed boot and recovery files before, as well as full ROMs but don't ever remember flashing a system file on its own.
Thanks!
Click to expand...
Click to collapse
I have the 1572 RETEU, but you can find the stock firmware here: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
If it's like the stock firmware that I have for the 1572 it should have all the img files and the system chunks. You just need to flash all the chunks like this:
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
This has to be done because Marshmallow doesn't allow any modification in the system or the boot image, and will not proceed with the OTA if the ROM is not full stock.
EDIT: You will not loose any data, but any modification to the system partition will be undone.
Dunkel06 said:
I managed to update via OTA flashing the stock recovery, boot and system chunks. This is the procedure I do to update my wife's Nexus 5 and worked for the Moto X Style too. Remember to make a backup before in case something goes wrong.
Click to expand...
Click to collapse
Thanks for your help once again. I manually flashed the system files like you listed, but for whatever reason, i'm still getting the same old Error. I'm pretty sure I'm on a stock ROM.
From this site: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I have flashed the XT1575 6.0 boot.img, recovery.img, then from the firmware, extracted the 8 sparsechunk files and flashed those as well. I still get the ERROR after a few seconds of trying to load the OTA.
Any other ideas by any chance? Did you do any kind of wiping in there somewhere? Did you just let the normal OTA try installing from within Android?
chuck-fu said:
Thanks for your help once again. I manually flashed the system files like you listed, but for whatever reason, i'm still getting the same old Error. I'm pretty sure I'm on a stock ROM.
From this site: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I have flashed the XT1575 6.0 boot.img, recovery.img, then from the firmware, extracted the 8 sparsechunk files and flashed those as well. I still get the ERROR after a few seconds of trying to load the OTA.
Any other ideas by any chance? Did you do any kind of wiping in there somewhere? Did you just let the normal OTA try installing from within Android?
Click to expand...
Click to collapse
I just let the normal OTA install after flashing system, boot and recovery, without wiping any partition. Maybe you can try a flash all the zip to make sure it's full stock and see if the OTA install. Just make a backup before in case nothing change.
Hello guys,
long time i had no problem (even that i couldnt make photos , use google play and had 4GB max space). I accidentaly erased system and through posts here i got custom chinese ROM with twrp(PLK-C00B618_Kangvip;EMUI 3.1; android 5.1.1). But now i want to make photos and use google play soo...any solutions ? I hope yes.
Thank you guys atleast for viewing this post.
You need to flash Google Framework and Google Play app, because most Chinese ROM removed those. You can flash a gapps package from Opengapps.
ARM-Android 5.1-Micro/Pico/Nano should do.
First get back to stock and then flash a custom ROM, this might help. Steps are below, follow them.
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
NOTE: If the manual flashing doesn't works or you get any errors, then first try only the force update method, i.e Putting the UPDATE.APP from which you extracted the files in dload folder of your external SDCARD and pressing Vol UP + Vol DOWN + Power button simultaneously after switching off your phone.
Thank you, just got time to try it so ill inform in 2h(slow download speed).
OMG!! man, tell me your adress so i can visit you and hug you, i tried so many times according to lot of posts and it havent worked. I gave up once, but now i finally, god bless, finally back to stock firmware, yaaaaaaaaaaaaaaay. Iam so happy, nothing can breaky my happiness for today.
Dont know why but i have only 4GB allocated storage(before accidental system remove i had 10). Can you help me with that too ?
Pixell9 said:
Dont know why but i have only 4GB allocated storage(before accidental system remove i had 10). Can you help me with that too ?
Click to expand...
Click to collapse
Did you flashed the UPDATE.APP again with three button reset method??
DigiGoon said:
Did you flashed the UPDATE.APP again with three button reset method??
Click to expand...
Click to collapse
Yes I did.
Pixell9 said:
Yes I did.
Click to expand...
Click to collapse
Those who followed this method didn't have this kinda problem.
Try to flash a custom ROM and see if anything changes.
---------- Post added at 01:02 AM ---------- Previous post was at 12:21 AM ----------
To flash custom ROM, you need to unlock your bootloader first, then flash TWRP recovery, and download any custom ROM of your choice and flash it via TWRP recovery.
DigiGoon said:
Those who followed this method didn't have this kinda problem.
Try to flash a custom ROM and see if anything changes.
---------- Post added at 01:02 AM ---------- Previous post was at 12:21 AM ----------
To flash custom ROM, you need to unlock your bootloader first, then flash TWRP recovery, and download any custom ROM of your choice and flash it via TWRP recovery.
Click to expand...
Click to collapse
Sorry that i havent responded for some time, but i dont have now much time, ill try it tommorow. Thx.
Pixell9 said:
Dont know why but i have only 4GB allocated storage(before accidental system remove i had 10). Can you help me with that too ?
Click to expand...
Click to collapse
Usually because partition is corrupted.
Reflash again boot, recovery, cust and system img files.
If still persists go down to B100 ROM and use its img files.
DigiGoon said:
Those who followed this method didn't have this kinda problem.
Try to flash a custom ROM and see if anything changes.
---------- Post added at 01:02 AM ---------- Previous post was at 12:21 AM ----------
To flash custom ROM, you need to unlock your bootloader first, then flash TWRP recovery, and download any custom ROM of your choice and flash it via TWRP recovery.
Click to expand...
Click to collapse
zinko_pt said:
Usually because partition is corrupted.
Reflash again boot, recovery, cust and system img files.
If still persists go down to B100 ROM and use its img files.
Click to expand...
Click to collapse
Thank you guys both, i just tried to manual flash update.app again through EMUi and it worked ^^.
Pixell9 said:
Thank you guys both, i just tried to manual flash update.app again through EMUi and it worked ^^.
Click to expand...
Click to collapse
No problem. Factory reset is also very important.
Pixell9 said:
Thank you guys both, i just tried to manual flash update.app again through EMUi and it worked ^^.
Click to expand...
Click to collapse
Glad it worked for you.
I'm new so please forgive me and my ignorance through all of this. I had a great root experience with my old LG G3, so when I got my Axon 7 (A2017U) I thought I'd try to root it too. I tried to follow DrakenFX's guide (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204) but I bit off more than I could chew. I got to the point where I had TWRP up, but this is where I think things started to fall apart. I was confused by the instructions and in a haste I continued anyway. In TWRP I went to Wipe>Format Data typed in yes like TWRP said and boom, I had no idea what happened. Rebooting only got a screen that said "Type in your password" but my passcode I had on the phone before it bricked didn't work. So by now I start panicking a bit. I thought I made a mistake earlier so I went back and tried to reinstall TWRP by putting the phone into EDL. The phone got stuck that way for a while, but I now I have it in TWRP. Right now, I just want to get back to safe stock android.
I'm 200% sure I messed with something I wasn't supposed to and I believe that is the system image(?)which Draken also linked (http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53). I'm downloading it as I type. I'm going to do my best to leave my phone just like it is right now, in TWRP, and wait for more advice on this before I do anything else.. What I'm curious about is where did I go wrong and what do I need to do to get my phone working again, preferably without returning it? Thank you for any advice you have to offer.
Update: It's worth noting I didn't know to enable OEM Unlocking when I was in stock android. Dumb move I know. I'm new here.
What software version are u on?
xiong77 said:
What software version are u on?
Click to expand...
Click to collapse
As far as I know I (was) on Android 6.0 A2017U B29. TWRP version 3.0.2-0
Get DrakenFX b29 mergeboot stack and b29 stock system and flash it then u should be OK. I did this too.
xiong77 said:
Get DrakenFX b29 mergeboot stack and b29 stock system and flash it then u should be OK. I did this too.
Click to expand...
Click to collapse
I tried, but the downloads take extremely long and are unreliable for me. I was downloading the stock system file at around 14 kbps and it eventually failed. Any other suggestions?
Wipe cache dalvik data and system reboot, ignore error message and reboot
---------- Post added at 06:54 AM ---------- Previous post was at 06:53 AM ----------
Try through ur computer
---------- Post added at 06:57 AM ---------- Previous post was at 06:54 AM ----------
Try go back to twrp and wipe like the op said
xiong77 said:
Wipe cache dalvik data and system reboot, ignore error message and reboot
---------- Post added at 06:54 AM ---------- Previous post was at 06:53 AM ----------
Try through ur computer
---------- Post added at 06:57 AM ---------- Previous post was at 06:54 AM ----------
Try go back to twrp and wipe like the op said
Click to expand...
Click to collapse
I've done the wipes multiple times. It's mostly the downloads I'm having trouble with. How and where do you get them? The links I found were dead or had a slow speed.
video_dewd said:
I've done the wipes multiple times. It's mostly the downloads I'm having trouble with. How and where do you get them? The links I found were dead or had a slow speed.
Click to expand...
Click to collapse
Did you save the recovery backup? If you did then use the axon7root.exe to flash the stock recovery. Then download the stock B20 from ZTE.
tabletalker7 said:
Did you save the recovery backup? If you did then use the axon7root.exe to flash the stock recovery. Then download the stock B20 from ZTE.
Click to expand...
Click to collapse
I've been able to find some recovery images that I found on other threads. The thing is, when I try to flash them on TWRP, I get an error about "/dev/block/sde14" being read-only.
video_dewd said:
I've been able to find some recovery images that I found on other threads. The thing is, when I try to flash them on TWRP, I get an error about "/dev/block/sde14" being read-only.
Click to expand...
Click to collapse
no no no no ..................... put phone in EDL mode. Copy the stock image into the folder with the axon7root.exe file you used to flash TWRP. Make sure the stock file is named recovery.img (or whatever the TWRP file is named in that folder, it has been a long time since I did this). Then use the axon7root.exe program the exact same way you did before. It will flash the stock recovery. Then in stock recovery you can flash the B20 from ZTE
tabletalker7 said:
no no no no ..................... put phone in EDL mode. Copy the stock image into the folder with the axon7root.exe file you used to flash TWRP. Make sure the stock file is named recovery.img (or whatever the TWRP file is named in that folder, it has been a long time since I did this). Then use the axon7root.exe program the exact same way you did before. It will flash the stock recovery. Then in stock recovery you can flash the B20 from ZTE
Click to expand...
Click to collapse
Ok, I will try this.
Update: I got the stock recovery back, but now I'm lost as to how to flash the stock b20 from zte. Thank you for all your help so far though.
video_dewd said:
Ok, I will try this.
Click to expand...
Click to collapse
got stock recovery working?
tabletalker7 said:
got stock recovery working?
Click to expand...
Click to collapse
Yes, I'm in the process of getting the update from sdcard feature working.
Update: Trying to use the update.zip file or unpacking it into the sdcard hasn't worked. Trying to use adb sideload returns "Cannot read 'update.zip'"
video_dewd said:
Yes, I'm in the process of getting the update from sdcard feature working.
Click to expand...
Click to collapse
ok - download it from zte. Put it on your SD card. In recovery select update from SD card. Be warned it will work but it is slow. Also note that while I will not say the bootloader unlock doesn't work on B29, I can say it worked flawlessly on B20. If you want unlocked I recommend doing so on B20.
tabletalker7 said:
ok - download it from zte. Put it on your SD card. In recovery select update from SD card. Be warned it will work but it is slow. Also note that while I will not say the bootloader unlock doesn't work on B29, I can say it worked flawlessly on B20. If you want unlocked I recommend doing so on B20.
Click to expand...
Click to collapse
I have the zip but it says, "Sorry,you can't sdcard upgrade".
video_dewd said:
I have the zip but it says, "Sorry,you can't sdcard upgrade".
Click to expand...
Click to collapse
try using adb sideload
---------- Post added at 07:48 AM ---------- Previous post was at 07:45 AM ----------
also people reportd sucess on the z-communities by placing the B20 on the internal sd card (phone storage)
tabletalker7 said:
try using adb sideload
---------- Post added at 07:48 AM ---------- Previous post was at 07:45 AM ----------
also people reportd sucess on the z-communities by placing the B20 on the internal sd card (phone storage)
Click to expand...
Click to collapse
I tried that. It won't accept the zip file and it's unclear which file to sideload. Would you happen to know? This is what files are in the unpacked zip. https://gyazo.com/c7546c3ed0dcb0972653eaeba42fcb40
video_dewd said:
I tried that. It won't accept the zip file and it's unclear which file to sideload. Would you happen to know? This is what files are in the unpacked zip. https://gyazo.com/c7546c3ed0dcb0972653eaeba42fcb40
Click to expand...
Click to collapse
Maybe - I'd have to download it to find out. If you can't get stock recovery to take it this post http://forum.xda-developers.com/showpost.php?p=69434328&postcount=17 gives you instructions on what lines to remove from the updater-script to make it flash in TWRP (I didn't have a problem making the stock B20 go in stock recovery, but I was unlocked at the time). You could reflash TWRP and try that.
Or just try this in TWRP http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
tabletalker7 said:
Maybe - I'd have to download it to find out. If you can't get stock recovery to take it this post http://forum.xda-developers.com/showpost.php?p=69434328&postcount=17 gives you instructions on what lines to remove from the updater-script to make it flash in TWRP (I didn't have a problem making the stock B20 go in stock recovery, but I was unlocked at the time). You could reflash TWRP and try that.
Or just try this in TWRP http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Click to expand...
Click to collapse
I'm going to try the first option. The second option's link take horrendously long to download.
Update: Trying to flash from TWRP results in error "Could not find 'META-INF/com/google/android/update-binary' which makes no sense since update binary is exactly where it should be.
Further Update: It seems that the problem might have been that when I compressed "update.zip" to fix "updater-script" it changed to file path by adding the title of the folder "update" to the beginning. I think that messed with the path giving the the meta-inf error.
video_dewd said:
I'm going to try the first option. The second option's link take horrendously long to download.
Update: Trying to flash from TWRP results in error "Could not find 'META-INF/com/google/android/update-binary' which makes no sense since update binary is exactly where it should be.
Click to expand...
Click to collapse
OK. How did you do that?
---------- Post added at 10:09 AM ---------- Previous post was at 09:54 AM ----------
Just suck it up and download the 2 b29 files. If it is that slow pick a different mirror
Hi there
Today I bought a pair of Bluetooth earphones and noticed that Bluetooth wasn't working anymore, so I decided to factory reset my vanilla ROM (EMUI 5.0).
That didn't work out and eventually I had to unlock the bootloader, flash a custom recovery (so far I tried both TWRP and Revolution) and a custom ROM.
However, something must have gone seriously bad because I now can't mount /product and /version.
When I try to install a rom (EliteROM by HassanMirza), it also tells me it couldn't load /cust and /data as well.
- cust: invalid argument
- data: invalid argument
- product: no such file or directory
- version: no such file or directory
I also tried moving an update.app version to my internal memory but doing that through gives me an error saying there's not enough space.
Pretty much at a loss here, no idea what to do. Anyone got an idea? Even willing to pay to get this fixed.
Can you access fastboot?
maartenw8 said:
Can you access fastboot?
Click to expand...
Click to collapse
I have access to fastboot and the Revolution recovery.
(thanks a lot in advance fellow Belgian )
LordInfernu said:
I have access to fastboot and the Revolution recovery.
(thanks a lot in advance fellow Belgian )
Click to expand...
Click to collapse
Great!! Use huawei update extractor (HERE) to extract all the .img files from the UPDATE.APP and try to flash them via fastboot.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
and so on
This should help you and your phone should boot.
------
Belgium ftw . Are you from the flanders?
maartenw8 said:
Great!! Use huawei update extractor (HERE) to extract all the .img files from the UPDATE.APP and try to flash them via fastboot.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
and so on
This should help you and your phone should boot.
------
Belgium ftw . Are you from the flanders?
Click to expand...
Click to collapse
I tried that yesterday, but flashing the system.img file gave an error, something like "sparse flash write failed".
Would you have any idea what the correct build would be for a Belgian VNS-L31 which was previously on EMUI 5.0.
I got my phone with a subscription from Proximus and after the update, it just completely broke (the software I mean).
I'm from Bruges! And you?
LordInfernu said:
I tried that yesterday, but flashing the system.img file gave an error, something like "sparse flash write failed".
Would you have any idea what the correct build would be for a Belgian VNS-L31 which was previously on EMUI 5.0.
I got my phone with a subscription from Proximus and after the update, it just completely broke (the software I mean).
I'm from Bruges! And you?
Click to expand...
Click to collapse
Hmmm.. Can you flash stock recovery and dload the firmware?
The build depends on your Cxxx. What is it? I also got my phone from proximus! Assuming you didn't debrand your phone, it should be C02, but maybe you did debrand. However, I would suggest trying to dload the rollback package because you were on nougat. You can find it here. Follow the instructions in the PDF file of the zip package. But first, extract the recovery from UPDATE.APP
---------------
Nice! I'm from Genk
maartenw8 said:
Hmmm.. Can you flash stock recovery and dload the firmware?
The build depends on your Cxxx. What is it? I also got my phone from proximus! Assuming you didn't debrand your phone, it should be C02, but maybe you did debrand. However, I would suggest trying to dload the rollback package because you were on nougat. You can find it here. Follow the instructions in the PDF file of the zip package. But first, extract the recovery from UPDATE.APP
---------------
Nice! I'm from Genk
Click to expand...
Click to collapse
Hmm so I've currently moved the update.app file to my external sd (if I'm correct this is the /external_sd/ folder - had to do this through adb because I don't have a card reader atm) and then tried to update by pressing on/off button, volume down, volume up. However, this just brings me back to my Revolution recovery. Should I flash the stock recovery first?
LordInfernu said:
Hmm so I've currently moved the update.app file to my external sd (if I'm correct this is the /external_sd/ folder - had to do this through adb because I don't have a card reader atm) and then tried to update by pressing on/off button, volume down, volume up. However, this just brings me back to my Revolution recovery. Should I flash the stock recovery first?
Click to expand...
Click to collapse
Yes flash stock recovery first! That way you'll have dload back
maartenw8 said:
Yes flash stock recovery first! That way you'll have dload back
Click to expand...
Click to collapse
Oh ok never gotten that far, great! So right now I did that but obviously I can't boot now.
I believe I now have to flash the full OS? Would it be ok if I flash TWRP or Revolution back just to use ADB and transfer the other update.app file, flash back to stock recovery and then use DLOAD method again?
Thanks so far for all the help, very much appreciated!
LordInfernu said:
Oh ok never gotten that far, great! So right now I did that but obviously I can't boot now.
I believe I now have to flash the full OS? Would it be ok if I flash TWRP or Revolution back just to use ADB and transfer the other update.app file, flash back to stock recovery and then use DLOAD method again?
Thanks so far for all the help, very much appreciated!
Click to expand...
Click to collapse
So you flashed the stock ROM and then you dload the Huawei Rollback package? Because if you flashed the rollback package you should be able to boot...
-----
Let me pm you to find a more easy way to communicate
maartenw8 said:
So you flashed the stock ROM and then you dload the Huawei Rollback package? Because if you flashed the rollback package you should be able to boot...
-----
Let me pm you to find a more easy way to communicate
Click to expand...
Click to collapse
Ah no I probably made a mistake. I'd definitely appreciate that!
LordInfernu said:
Ah no I probably made a mistake. I'd definitely appreciate that!
Click to expand...
Click to collapse
I sent you a message
i'm having the same problem here (also from Belgium)
anyone willing to guide me through?
thanks
Same problem here, the link to rollback package is invalid. Is there someone kind enough to help us out?
lepraook said:
i'm having the same problem here (also from Belgium)
anyone willing to guide me through?
thanks
Click to expand...
Click to collapse
What recovery are you using?
---------- Post added at 06:13 AM ---------- Previous post was at 06:13 AM ----------
VonHornmeister said:
Same problem here, the link to rollback package is invalid. Is there someone kind enough to help us out?
Click to expand...
Click to collapse
What recovery are you using?
maartenw8 said:
What recovery are you using?
---------- Post added at 06:13 AM ---------- Previous post was at 06:13 AM ----------
What recovery are you using?
Click to expand...
Click to collapse
Twrp
Exact version.have to check
Also after reflashing recovery system boot i can.reboot
I'm on android 6 now with dual.sim instead of single
Had to flash this info to phone to get him.going
lepraook said:
Twrp
Exact version.have to check
Also after reflashing recovery system boot i can.reboot
I'm on android 6 now with dual.sim instead of single
Had to flash this info to phone to get him.going
Click to expand...
Click to collapse
Hi there. I am stuck. Are you willing to help me please?
---------- Post added at 12:55 AM ---------- Previous post was at 12:28 AM ----------
LordInfernu said:
Hi there
Today I bought a pair of Bluetooth earphones and noticed that Bluetooth wasn't working anymore, so I decided to factory reset my vanilla ROM (EMUI 5.0).
That didn't work out and eventually I had to unlock the bootloader, flash a custom recovery (so far I tried both TWRP and Revolution) and a custom ROM.
However, something must have gone seriously bad because I now can't mount /product and /version.
When I try to install a rom (EliteROM by HassanMirza), it also tells me it couldn't load /cust and /data as well.
- cust: invalid argument
- data: invalid argument
- product: no such file or directory
- version: no such file or directory
I also tried moving an update.app version to my internal memory but doing that through gives me an error saying there's not enough space.
Pretty much at a loss here, no idea what to do. Anyone got an idea? Even willing to pay to get this fixed.
Click to expand...
Click to collapse
hey dude. I have a similar problem and I just can't solve it. Did you ever get your phone working again?