Related
Hello,
i'm reading here for some weeks and this forum helped me much so far. Now I made a bad mistake while flashing the latest firmware on my One and it seems that I have bricked it.
What have I done?
I used ARHD 5.1 GE on my One with an older firmware. Before that I was using ARHD 4.1. Data of my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4260mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I changed to SuperCID, before that I had VODAP102. Bootloader is relocked.
After flashing latest firmware, my sdcard got wiped. So I have no backups or any other data on my phone. The phone stops booting after the white screen with the "HTC" logo and shows a turquoise color with little stripes and nothing happens.
I tried to flash another firmware, as you can see in the phone's details. That worked, but changed nothing. I can't install a rom, because adb doesn't find my device, but fastboot does. I tried several HTC-drivers and cables and USB-slots. Nothing.
I read several How-To's but I got stuck with this. Even tried to install the 1.28.401.7 RUU, but that stops with Error 155. After first time that error occured I relocked my bootloader, but that didn't help. I can't push files to the phone, because adb doesn't work.
Now only one thing left: Asking you for help. I'm somewhat frustrated.
Peko
pekomane said:
Hello,
i'm reading here for some weeks and this forum helped me much so far. Now I made a bad mistake while flashing the latest firmware on my One and it seems that I have bricked it.
What have I done?
I used ARHD 5.1 GE on my One with an older firmware. Before that I was using ARHD 4.1. Data of my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
I changed to SuperCID, before that I had VODAP102. Bootloader is relocked.
After flashing latest firmware, my sdcard got wiped. So I have no backups or any other data on my phone. The phone stops booting after the white screen with the "HTC" logo and shows a turquoise color with little stripes and nothing happens.
I tried to flash another firmware, as you can see in the phone's details. That worked, but changed nothing. I can't install a rom, because adb doesn't find my device, but fastboot does. I tried several HTC-drivers and cables and USB-slots. Nothing.
I read several How-To's but I got stuck with this. Even tried to install the 1.28.401.7 RUU, but that stops with Error 155. After first time that error occured I relocked my bootloader, but that didn't help. I can't push files to the phone, because adb doesn't work.
Now only one thing left: Asking you for help. I'm somewhat frustrated.
Peko
Click to expand...
Click to collapse
1- remove IMEI and s/n
2- install latest TWRP 2.6.3.3 (needed for 4.4 roms)
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: http://techerrata.com/browse/twrp2/m7 don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
3- confirm adb working in TWRP now, and unlock using: http://forum.xda-developers.com/showthread.php?t=2475914 or "revone -u"
(you don't need to relock if you're s-off)
4- push, sideload, or OTG a ROM and install
5- error 155 occurs due to hboot 1.55+, you'll need to downgrade to 1.44 to run RUU
nkk71 said:
1- remove IMEI and s/n
2- install latest TWRP 2.6.3.3 (needed for 4.4 roms)
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: http://techerrata.com/browse/twrp2/m7 don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
3- confirm adb working in TWRP now, and unlock using: http://forum.xda-developers.com/showthread.php?t=2475914 or "revone -u"
(you don't need to relock if you're s-off)
4- push, sideload, or OTG a ROM and install
5- error 155 occurs due to hboot 1.55+, you'll need to downgrade to 1.44 to run RUU
Click to expand...
Click to collapse
Step 1 already edited, right after posting...
Thanks for now, I have to try that when I am at home. I will post here, if it worked or not.
pekomane said:
Step 1 already edited, right after posting...
Thanks for now, I have to try that when I am at home. I will post here, if it worked or not.
Click to expand...
Click to collapse
no problem, IF you're gonna end up using RUU, you need to downgrade to this hboot: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then go to bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <- just in case the first one says "failed flush again"
fastboot reboot-bootloader
and run the RUU, should work fine.
nkk71 said:
no problem, IF you're gonna end up using RUU, you need to downgrade to this hboot: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then go to bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <- just in case the first one says "failed flush again"
fastboot reboot-bootloader
and run the RUU, should work fine.
Click to expand...
Click to collapse
Thanks for that, but using RUU was only one way I thought of to get my phone working again, because adb push and sideload don't work. If the way you mentioned in your first post works, then I will be absolutely fine without using RUU. Otherwise I will try the RUU option.
It worked! Thanks for your help! :good:
pekomane said:
It worked! Thanks for your help! :good:
Click to expand...
Click to collapse
Cool, if everything OK now, could you edit main thread title to include [SOLVED], Danke
Done.
By the way, it was the first option you posted that did the trick.
pekomane said:
Done.
By the way, it was the first option you posted that did the trick.
Click to expand...
Click to collapse
Sent from my HTC One using Tapatalk
Hello nkk7
S-OFF by rumrunners
bootloader 1.55
Version main 3.62.401.1
Cid HTC001
Mid pn0710000
I have tu use ruu to go back to stock can u please give me step by step guide in sequence pls
Pls
And there is no ruu for 3.62.401.1
Thus I will have downgrade that's why I am confused
Pls give me step by step info
shurahbil said:
Hello nkk7
S-OFF by rumrunners
bootloader 1.55
Version main 3.62.401.1
Cid HTC001
Mid pn0710000
I have tu use ruu to go back to stock can u please give me step by step guide in sequence pls
Pls
And there is no ruu for 3.62.401.1
Thus I will have downgrade that's why I am confused
Pls give me step by step info
Click to expand...
Click to collapse
follow my guide in my signature, there is a RUU.EXE available for CID: HTC__001 and MID: PN0710000 (so you can follow the RUU.EXE procedure)
in my opinion do NOT GO S-ON!!
nkk71 said:
follow my guide in my signature, there is a RUU.EXE available for CID: HTC__001 and MID: PN0710000 (so you can follow the RUU.EXE procedure)
in my opinion do NOT GO S-ON!!
Click to expand...
Click to collapse
Done ok ty
Why do not go s-on
Because you will close an avenue of troubleshooting if you are S-ON..
my htc one was stuck in bootloop i try a ruu with no success after that by fastboot unlocked the bootloader, flash a custom recovery (TWRP) and accidental wipe the phone, now i cant flash any zip give me the message unable to mount /data/
i try many roms by push fastboot and by otg cable no success
this is the result of fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: erased by me
(bootloader) imei: erased by me
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
thanks in advance
mendek said:
my htc one was stuck in bootloop i try a ruu with no success after that by fastboot unlocked the bootloader, flash a custom recovery (TWRP) and accidental wipe the phone, now i cant flash any zip give me the message unable to mount /data/
i try many roms by push fastboot and by otg cable no success
this is the result of fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: erased by me
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
thanks in advance
Click to expand...
Click to collapse
I would also remove your serialno! Follow the steps in this post. You can use TWRP 2.6.3.3 or TWRP 2.7.1.2 as well as the one in the post.
majmoz said:
I would also remove your serialno! Follow the steps in this post. You can use TWRP 2.6.3.3 or TWRP 2.7.1.2 as well as the one in the post.
Click to expand...
Click to collapse
thank you but where i can find a ruu to my device ? because i have the last ota update before brick
mendek said:
thank you but where i can find a ruu to my device ? because i have the last ota update before brick
Click to expand...
Click to collapse
I couldn't find a RUU for your phone, but here is a nandroid backup use Method 2. If you need the stock firmware you can get it here to run it your bootloader must be LOCK/RELOCK.
majmoz said:
I couldn't find a RUU for your phone, but here is a nandroid backup use Method 2. If you need the stock firmware you can get it here to run it your bootloader must be LOCK/RELOCK.
Click to expand...
Click to collapse
I Flash firmware, unlock the bootloader and restore a nandroid, clear cache, when reboot after HTC logo It makes a horrible noise, White screen and turn off
mendek said:
I Flash firmware, unlock the bootloader and restore a nandroid, clear cache, when reboot after HTC logo It makes a horrible noise, White screen and turn off
Click to expand...
Click to collapse
If I am following you correctly these are the steps you took:
First you flashed the firmware. Which firmware did you flash?
Then you unlocked the bootloader and installed a custom recovery. Which recovery?
Then you restored the nandroid from the post. Did you select root after the nandroid installed?
Then you cleared cache? Why?
majmoz said:
If I am following you correctly these are the steps you took:
First you flashed the firmware. Which firmware did you flash?
Then you unlocked the bootloader and installed a custom recovery. Which recovery?
Then you restored the nandroid from the post. Did you select root after the nandroid installed?
Then you cleared cache? Why?
Click to expand...
Click to collapse
hi flash the last firmware from the ota i has before.
after that flash twrp recovery 2.7.1
select root when restore
clear cache for no reason
but now i can enter in recovery always stuck in entering recovery, tried many versions of twrp and cwm and nothing, try fastboot erase cache no results
now only enter fastboot
already try relock the bootloader and flash firmware, unlock again flash custom recovery but still the same
i really dont know what do next...
mendek said:
hi flash the last firmware from the ota i has before.
after that flash twrp recovery 2.7.1
select root when restore
clear cache for no reason
but now i can enter in recovery always stuck in entering recovery, tried many versions of twrp and cwm and nothing, try fastboot erase cache no results
now only enter fastboot
already try relock the bootloader and flash firmware, unlock again flash custom recovery but still the same
i really dont know what do next...
Click to expand...
Click to collapse
I think the firmware you are using is not a compete package, generally firmware removed from OTA don't have all of the elements just those needed to run the OTA. Get a .401 stock firmware from this Placeholder of HTC One Firmwares.
majmoz said:
I think the firmware you are using is not a compete package, generally firmware removed from OTA don't have all of the elements just those needed to run the OTA. Get a .401 stock firmware from this Placeholder of HTC One Firmwares.
Click to expand...
Click to collapse
which firmware ? i try many but always failed in signature verification
mendek said:
hi flash the last firmware from the ota i has before.
after that flash twrp recovery 2.7.1
select root when restore
clear cache for no reason
but now i can enter in recovery always stuck in entering recovery, tried many versions of twrp and cwm and nothing, try fastboot erase cache no results
now only enter fastboot
already try relock the bootloader and flash firmware, unlock again flash custom recovery but still the same
i really dont know what do next...
Click to expand...
Click to collapse
Hello, i'm sorry i don't know what to say because i have almost the same problem, my htc one m7_UL won't start...is shutsdown sometimes at boot time, when i take photos with it...and sometimes what ever else, but in recovery mode it can still houers and houers. yesterday i brought it to s-off then i installed an RUU...but still the same problem !!! is it a material issue ??? thank you.
Within TWRP you should wipe data (not custom) to recreate data, system, and etc. folders. This will also wipe whats on you sdcard so, you'll have to adb push new files to your sdcard to flash a rom.
ZikoMikoo said:
Hello, i'm sorry i don't know what to say because i have almost the same problem, my htc one m7_UL won't start...is shutsdown sometimes at boot time, when i take photos with it...and sometimes what ever else, but in recovery mode it can still houers and houers. yesterday i brought it to s-off then i installed an RUU...but still the same problem !!! is it a material issue ??? thank you.
Click to expand...
Click to collapse
my start exactly like yours random restarts etc, after unlock bootloader works for another week and when i playing a game turn off and never can put it work again, now even cant enter recovery
mendek said:
which firmware ? i try many but always failed in signature verification
Click to expand...
Click to collapse
5.11.401.10
majmoz said:
5.11.401.10
Click to expand...
Click to collapse
i flash this firmware, unlock bootloader flash twrp now when is enter in recovery i see the twrp logo and after that reboot and stay in a bootloop
mendek said:
i flash this firmware, unlock bootloader flash twrp now when is enter in recovery i see the twrp logo and after that reboot and stay in a bootloop
Click to expand...
Click to collapse
after flashing a recovery, you also need to
Code:
fastboot erase cache
majmoz said:
5.11.401.10
Click to expand...
Click to collapse
now i can access the recovery, if i restore whe it pass the htc logo stucks with some stripes in the screen and turn off, try flash cyanogen it turn on but some times stucks and reboots i dont what to do maybe hardware fault?
mendek said:
now i can access the recovery, if i restore whe it pass the htc logo stucks with some stripes in the screen and turn off, try flash cyanogen it turn on but some times stucks and reboots i dont what to do maybe hardware fault?
Click to expand...
Click to collapse
Try to get back into TWRP, in TWRP flash this stock ROM Method 1. I am guessing that when you say you restore that you are talking about the nandroid backup you got from the site.
Hi guys,
I have a big problem with my HTC One. I wanted to give it to the service, but it costs a lot of money, maybe I will find some help on XDA hopefully.
My bootloader info looks like this:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.57.0000
RADIO- 4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.11.401.10
eMMC-boot 2048MB
May 5 2014,23:16:29.0
I deleted my system partition in twrp recovery. I can get only to bootloader and recovery. I am S-ON all the time, cannot get S-OFF, I get errors all the time using rum runner or firewater. When I type fastboot oem lock, I am stuck in bootloader, cannot enter recovery. Then the bootloader says ***TAMPERED*** ***RELOCKED*** ***SECURITY WARNING***. I really don't know what to do, I'm stuck. Please help :C !!!
Thanks
My fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4332mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.099s
GalaXxXx said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4332mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.099s
Click to expand...
Click to collapse
You should remove your imei and serialno in your previous post. You can use this stock rom zip to go back to stock. It is the same version that you have. Your bootloader must be LOCKED or RELOCKED. Move the file to your adb/fastboot folder and rename it rom.zip. Open a command window on the same folder then type the following:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip rom.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip rom.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Thanks a lot @majmoz
I'm downloading zip file now (slow internet 2 hours remaining). I will try your method, and let you know how it went.
doesn't work ;/
@majmoz , it doesn't work .
I did everything you said and when flashing it says "FAILED (remote: 12 signature verify fail)". Did this command 2 times as you instructed.
The second thing is that the "adb reboot bootloader" command didn't work, cmd said that device not found.
What should I do ?
GalaXxXx said:
@majmoz , it doesn't work .
I did everything you said and when flashing it says "FAILED (remote: 12 signature verify fail)". Did this command 2 times as you instructed.
The second thing is that the "adb reboot bootloader" command didn't work, cmd said that device not found.
What should I do ?
Click to expand...
Click to collapse
Does you bootloader still say "Relocked"? Let try to run the stock firmware 5.11.401.10 using the same method, just rename the download to firmware.zip change the rom.zip in the procedure to firmware.zip.
For adb not working take a look at FAQ Q#2.
My bootloader says TAMPERED RELOCKED SECURITY WARNING
I don't think adb works in bootloader, right ?
The firmware.zip worked, (there was the green bar etc.), but the phone is still not rebooting into system.
hmm... there is no custom recovery anymore, just a phone with red sign. And in bootloader it says only tampered and relocked. Without security warning. @majmoz
GalaXxXx said:
My bootloader says TAMPERED RELOCKED SECURITY WARNING
I don't think adb works in bootloader, right ?
The firmware.zip worked, (there was the green bar etc.), but the phone is still not rebooting into system.
hmm... there is no custom recovery anymore, just a phone with red sign. And in bootloader it says only tampered and relocked. Without security warning. @majmoz
Click to expand...
Click to collapse
You are correct adb does not work in bootloader. When the firmware completed it installed the stock recovery. Since you erased the system partition there is no OS installed. You can try to run the RUU again and it will probably pass now since you have the correct firmware. If this is successful, you will have stock rom and stock firmware on your phone.
What did you mean by give to service?
majmoz said:
You are correct adb does not work in bootloader. When the firmware completed it installed the stock recovery. Since you erased the system partition there is no OS installed. You can try to run the RUU again and it will probably pass now since you have the correct firmware. If this is successful, you will have stock rom and stock firmware on your phone.
What did you mean by give to service?
Click to expand...
Click to collapse
There is an unbrick service here in the forum
I would imagine that's what he's referring to
You are correct adb does not work in bootloader. When the firmware completed it INSTALLED the stock recovery. Since you erased the system partition there is no OS installed. You can try to run the RUU again and it will probably pass now since you have the correct firmware. If this is successful, you will have stock rom and stock firmware on your phone.
What did you mean by give to service?
Click to expand...
Click to collapse
There is an unbrick service here in the forum
I would imagine that's what he's referring to
Click to expand...
Click to collapse
No no, I have a service nearby here in my town. They said they can restore the phone for $30.
I will try the RUU file now, hope it works. I'll be informing what is the status of my "operation" @majmoz @ajbiz11
P.S. How to quote ? You know (Originally Posted by etc.)
GalaXxXx said:
I did everything you said and when flashing it says "FAILED (remote: 12 signature verify fail)".
Click to expand...
Click to collapse
@majmoz I don't think this zip can be flashed using "fastboot flash zip rom.zip", with s-on he can only flash signed ruu from HTC and afaik, htc never released any 5.11.401.10 signed ruu
There is a flashable aroma zip (guru reset) for his version here: https://www.androidfilehost.com/?fid=23501681358543706
to be flashed with a custom recovery (require to unlock the bootloader again)
Yeah @alray , I need to have a 5.11.401.10 signed RUU, but there is no such file avaible to download.
Now, I will unlock my bootloader again, flash custom recovery (TWRP) , and try flash guru reset in this recovery.
Well, I don't really remember, but I think I tried this (maybe with not the same version of guru reset), but I was stuck on "Installation procces" It was 0 % all the time. Let's see how it works out this time with this version of guru.
@alray
I unlocked my bootloader, flashed TWRP, I used adb to push the .zip to sdcard, but the problem now is that the phone says that unable to mount '/data' and unable to mount internal storage. When I click mount in recovery the "data" box doesn't wanna tick .
What should I do ? I'm tired of this ...
Ok, what happened next... I finally did what @alray told me to do. I managed to fix the corrupted data partition, but as I said earlier, when I flash the guru reset in recovery, and start the installation process, it is stuck on 0.00%.
I unlocked the bootloader in order to do this.
No more ideas ? @majmoz ?
GalaXxXx said:
Ok, what happened next... I finally did what @alray told me to do. I managed to fix the corrupted data partition, but as I said earlier, when I flash the guru reset in recovery, and start the installation process, it is stuck on 0.00%.
I unlocked the bootloader in order to do this.
No more ideas ? @majmoz ?
Click to expand...
Click to collapse
What version of TWRP are you using? 2.6.3.3 or 2.8.0.1? I'm pretty sure you checked the MD5 of the files you downloaded.
I'm using TWRP v2.8.0.2. What do you mean by saying you're pretty sure I checked the MD5? I didn't .. @majmoz
GalaXxXx said:
I'm using TWRP v2.8.0.2. What do you mean by saying you're pretty sure I checked the MD5? I didn't .. @majmoz
Click to expand...
Click to collapse
You should always check the MD5 of downloaded files to ensure they did not get corrupted during the downloading process. The MD5 is generally noted on the download site. Here is a how to check the MD5.
I also recommend to use 2.6.3.3 instead of 2.8+
Ohh my god, finally did it !!! Thank you a lot guys !!! I was trying guru reset earlier with unlocked bootloader too, but the twrp version was wrong... ohh, everything because of this new version of twrp.... But thanks, I have my system back . I will be able to do OTA updates now ?
@majmoz @alray
GalaXxXx said:
Ohh my god, finally did it !!! Thank you a lot guys !!! I was trying guru reset earlier with unlocked bootloader too, but the twrp version was wrong... ohh, everything because of this new version of twrp.... But thanks, I have my system back . I will be able to do OTA updates now ?
@majmoz @alray
Click to expand...
Click to collapse
you should be able to do ota if you have selected to install stock recovery in the aroma installer.
Hello there !
I got a prolem with my htc one international.
For a while i had a custom rom and decided to go back to stock rom. After some time trying to go back to stock i got som problems now.
i had TWRP on the phone, and i flashed another recovery.img, now my recovery looks all weird. i'll attach a screenshot from.
Now i cant get my old recovery i have tried everything. is there anybody out there to help me !!
(on the image you can see how it looks after trying an OTA installation)
Dardo27 said:
Hello there !
I got a prolem with my htc one international.
For a while i had a custom rom and decided to go back to stock rom. After some time trying to go back to stock i got som problems now.
i had TWRP on the phone, and i flashed another recovery.img, now my recovery looks all weird. i'll attach a screenshot from.
Now i cant get my old recovery i have tried everything. is there anybody out there to help me !!
(on the image you can see how it looks after trying an OTA installation)
Click to expand...
Click to collapse
Nearly every thread in this section has something to do with not being able to update from kitkat to lollipop on rooted phone.
did you read any of those and try anything before asking for help ?
you make no mention of what phone you have
you need a stock system and stock recovery to take OTA updates have you flash a stock rom before the stock recovery ?
clsA said:
Nearly every thread in this section has something to do with not being able to update from kitkat to lollipop on rooted phone.
did you read any of those and try anything before asking for help ?
you make no mention of what phone you have
you need a stock system and stock recovery to take OTA updates have you flash a stock rom before the stock recovery ?
Click to expand...
Click to collapse
Sure i do mention what phone i have, HTC one m7 !!! and u can see the pic !
i have read many posts on the internet, tried a lot to go back to stock, am on stock right now, the only problem is my recovery mode !
Dardo27 said:
Sure i do mention what phone i have, HTC one m7 !!! and u can see the pic !
Click to expand...
Click to collapse
There is many versions of the M7. You need to post the output of "fastboot getvar all" like we ask in every threads here so we can know exactly what phone you have and which sofmtware/firmware version installed, CID and MID number, S-ON or S-OFF.
i have read many posts on the internet, tried a lot to go back to stock, am on stock right now, the only problem is my recovery mode !
Click to expand...
Click to collapse
What recovery version have you flashed exactly?
Waiting for your "fastboot getvar all" output (remove imei and serialno befor eposting).
Dardo27 said:
Sure i do mention what phone i have, HTC one m7 !!! and u can see the pic !
i have read many posts on the internet, tried a lot to go back to stock, am on stock right now, the only problem is my recovery mode !
Click to expand...
Click to collapse
start by making sure you have the correct stock recovery, look wrong to me, so have a look through the general section for a thread labelled "stock recovery collection" and then download the 6.09.401.11 (your firmware) recovery and flash it, then try and update again.
alray said:
There is many versions of the M7. You need to post the output of "fastboot getvar all" like we ask in every threads here so we can know exactly what phone you have and which sofmtware/firmware version installed, CID and MID number, S-ON or S-OFF.
What recovery version have you flashed exactly?
Waiting for your "fastboot getvar all" output (remove imei and serialno befor eposting).
Click to expand...
Click to collapse
Here you go !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4067mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I do not exactly remember what version of recovery it was, but i think was a stockrecovery with the wrong version from what i need!
i locked my bootloader and have no root anymore !!
thank u for your help !
Dardo27 said:
Here you go !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4067mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I do not exactly remember what version of recovery it was, but i think was a stockrecovery with the wrong version from what i need!
i locked my bootloader and have no root anymore !!
thank u for your help !
Click to expand...
Click to collapse
you must use the 6.09.401.11 stock recovery. Since you have re-locked the bootloader, you'll have to unlock it again, restore the stock rom again and then flash the 6.09.40.11 stock recovery so you can use ota updates. No need to relock the bootloader
6.09.401.11 stock recovery here: https://www.androidfilehost.com/?fid=95832962473395870
6.09.401.11 twrp nandroid backup here: https://www.androidfilehost.com/?fid=95832962473396067
Seanie280672 said:
start by making sure you have the correct stock recovery, look wrong to me, so have a look through the general section for a thread labelled "stock recovery collection" and then download the 6.09.401.11 (your firmware) recovery and flash it, then try and update again.
Click to expand...
Click to collapse
i have tried that, this is what i get " (bootloader) signature checking...
FAILED (remote: signature verify fail)"
dont know if i'm using the right method for flash.
Dardo27 said:
i have tried that, this is what i get " (bootloader) signature checking...
FAILED (remote: signature verify fail)"
dont know if i'm using the right method for flash.
Click to expand...
Click to collapse
Failed to flash cos your bootloader is re-locked.
See @alray post above, you will have to start again, you dont need to lock or re-lock the bootloader for an OTA.
Fingerprint error as per your picture is a firmware issue, and as recovery is the only thing you can change whilst s-on, its a wrong recovery error.
the picture says it expects to find 366813.11 (.11 your firmware) but found something different, so failed.
alray said:
you must use the 6.09.401.11 stock recovery. Since you have re-locked the bootloader, you'll have to unlock it again, restore the stock rom again and then flash the 6.09.40.11 stock recovery so you can use ota updates. No need to relock the bootloader
okej ! so first i restore with twrp and then flash it ! do i need to root to use the nandroid for the restore ? or could i just use cmd ?
Thank u for your help !! reallyyyy !!:good:
Click to expand...
Click to collapse
Dardo27 said:
okej ! so first i restore with twrp and then flash it ! do i need to root to use the nandroid for the restore ? or could i just use cmd ?
Thank u for your help !! reallyyyy !!:good:
Click to expand...
Click to collapse
unlock the bootloader
flash twrp recovery
restore the nandroid backup linked above
flash back the stock recovery linked above
alray said:
unlock the bootloader
flash twrp recovery
restore the nandroid backup linked above
flash back the stock recovery linked above
Click to expand...
Click to collapse
do i flash the stock recovery with fastboot or just install with twrp ?
sorry for all the questions...thnx for the help
Dardo27 said:
do i flash the stock recovery with fastboot or just install with twrp ?
sorry for all the questions...thnx for the help
Click to expand...
Click to collapse
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Dardo27 said:
do i flash the stock recovery with fastboot or just install with twrp ?
sorry for all the questions...thnx for the help
Click to expand...
Click to collapse
If your using TWRP 2.8.5.0 you can flash the recovery.img right from TWRP
clsA said:
If your using TWRP 2.8.5.0 you can flash the recovery.img right from TWRP
Click to expand...
Click to collapse
interesting, how its done? I suppose we must have the recovery image on /sdcard and then we can flash it from the "install" menu?
alray said:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
looks like i got a red triangle now when i try to get into recovery mode
Dardo27 said:
looks like i got a red triangle now when i try to get into recovery mode
Click to expand...
Click to collapse
its normal, this is the stock recovery screen, reboot your phone in the os and check for updates.
alray said:
its normal, this is the stock recovery screen, reboot your phone in the os and check for updates.
Click to expand...
Click to collapse
should there not be like a menu for wipe and stuff ?? now its just a red triangle nothing more ?
Dardo27 said:
should there not be like a menu for wipe and stuff ?? now its just a red triangle nothing more ?
Click to expand...
Click to collapse
the menu is revealed by holding volume up and hitting power.
alray said:
the menu is revealed by holding volume up and hitting power.
Click to expand...
Click to collapse
info
What's new in 2.8.4.0:
Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
Fix some MTP related crashes and bugs
Eliminate TWRP toggling USB IDs during boot if MTP is enabled
Fix various adb sideload issues
Improve threading of actions
Eliminate separate thread for screen timeout
Update libblkid to 2.25.0
Use power button as back button on watch themes for easier navigation
Add mutex locking to data manager
Improve custom theme handling on encrypted devices
Click to expand...
Click to collapse
Hi everyone
Been on Cyanogenmod 11-20140424-NIGHTLY-M7 for far too long and wanted to either upgrade Cyanogenmod or, better yet, move to Viper. I'm somewhat skilled with Windows and Linux, but I can't seem getting things to work.
What I've got:
HTC One M7 (unbranded, bought in Switzerland)
Unlocked S-ON
hboot: 1.44.0000
M7-UL PVT SHIP S-ON RH
RADIO-4A.14.3250.13
OpenDSP-v26-120-274-0202
CID: HTC_102
It's rooted and got CWM ROM-Manager installed
Notebook with Windows 8.1, USB 3.0 all around
What I've tried so far:
Getting S-OFF
- Did not work. revone throws an ERROR=1 at me when I try to ./revone -P. I've tried like a hundred times, with su and all.
Then I tried to relock and get an RUU on it:
- Relocking did not work. Neither with revone (./revone -l or -r is successful on the CLI, but does nothing, i.e. still says *** UNLOCKED *** in the bootloader), nor with fastboot...
- ... as fastboot does not work, either. Tried different drivers and all, but fastboot always says < waiting for device >. So fastboot oem lock achieved nothing, either.
Then I just tried to install an RUU to get to JB and hboot 1.55 to then continue with rumrunner. This got stuck at some boot-image showing the HTC logo and the .exe cancelled.
Is USB3.0 breaking my neck here or do I have any other options to get to ViperOne?
Thanks in advance...
From what i've read in here many times, hboot 1.44 isn't compatiable with windows 8. 1. You need to use a windows 7 machine.
dorsetqpr said:
From what i've read in here many times, hboot 1.44 isn't compatiable with windows 8. 1. You need to use a windows 7 machine.
Click to expand...
Click to collapse
Correct
Hoelli169 said:
Hi everyone
Been on Cyanogenmod 11-20140424-NIGHTLY-M7 for far too long and wanted to either upgrade Cyanogenmod or, better yet, move to Viper. I'm somewhat skilled with Windows and Linux, but I can't seem getting things to work.
What I've got:
HTC One M7 (unbranded, bought in Switzerland)
Unlocked S-ON
hboot: 1.44.0000
M7-UL PVT SHIP S-ON RH
RADIO-4A.14.3250.13
OpenDSP-v26-120-274-0202
CID: HTC_102
It's rooted and got CWM ROM-Manager installed
Notebook with Windows 8.1, USB 3.0 all around
What I've tried so far:
Getting S-OFF
- Did not work. revone throws an ERROR=1 at me when I try to ./revone -P. I've tried like a hundred times, with su and all.
Then I tried to relock and get an RUU on it:
- Relocking did not work. Neither with revone (./revone -l or -r is successful on the CLI, but does nothing, i.e. still says *** UNLOCKED *** in the bootloader), nor with fastboot...
- ... as fastboot does not work, either. Tried different drivers and all, but fastboot always says < waiting for device >. So fastboot oem lock achieved nothing, either.
Then I just tried to install an RUU to get to JB and hboot 1.55 to then continue with rumrunner. This got stuck at some boot-image showing the HTC logo and the .exe cancelled.
Is USB3.0 breaking my neck here or do I have any other options to get to ViperOne?
Thanks in advance...
Click to expand...
Click to collapse
Windows 8 and hboot 1.44 are not compatible. You should use Windows 7 or better still Linux (preferably ubuntu 32bit)
Sent from my M7 ARHD 84-Kitkat
OK, got my hands on a Linux notebook and managed the relock the bootloader. This led to only being able to boot into Bootloader, Recovery and ROM did always boot into Bootloader.
Then I tried to get a RUU with JB4.3 on the device to be able to run rumrunner on hboot 1.55.
#sudo fastboot flash zip RUU.zip
sending 'zip' (1065710 KB)...
OKAY [ 59.411s}
writing 'zip' ...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.238s
Now I unlocked the bootloader again to at least be able to boot into CYM again.
Meh, I'm kinda lost here. I feel confused about RUUs, CIDs, Nandroid Backups and where to go from here.
Any ideas?
Edit:*Here's the fastboot-info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Edit2:*OK, I'm stuck in the CYM*launcher. Really kinda lost now D:
Hoelli169 said:
OK, got my hands on a Linux notebook and managed the relock the bootloader. This led to only being able to boot into Bootloader, Recovery and ROM did always boot into Bootloader.
Then I tried to get a RUU with JB4.3 on the device to be able to run rumrunner on hboot 1.55.
#sudo fastboot flash zip RUU.zip
sending 'zip' (1065710 KB)...
OKAY [ 59.411s}
writing 'zip' ...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.238s
Now I unlocked the bootloader again to at least be able to boot into CYM again.
Meh, I'm kinda lost here. I feel confused about RUUs, CIDs, Nandroid Backups and where to go from here.
Any ideas?
Edit:*Here's the fastboot-info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Edit2:*OK, I'm stuck in the CYM*launcher. Really kinda lost now D:
Click to expand...
Click to collapse
Download this recovery. http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Put the file in your fastboot folder.
Download this Rom. Put the zip in your fastboot folder and rename it rom.zip
http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Select recovery from the bootloader menu. While in TWRP recovery. Push the Rom. Type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push us complete. Do a full wipe and install the Rom. During the install setup choose these options.
Stock recovery = yes
Stock radio = yes
Root = No
You will now have full stock Rom and recovery. Reboot the device and go to settings>about>Software Updates. Download and install the OTA update. Repeat process untill your on JB 3.xx.401.x firmware. Then use rumrunner to gain s-off. :good:
Sent from my M7 ARHD 84-Kitkat
Danny201281 said:
Download this recovery.
Put the file in your fastboot folder.
Download this Rom. Put the zip in your fastboot folder and rename it rom.zip
Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Worked!
Select recovery from the bootloader menu. While in TWRP recovery. Push the Rom. Type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push us complete. Do a full wipe and install the Rom. During the install setup choose these options.
Click to expand...
Click to collapse
This didn't work. While in TWRP, adb was not able to connect. Funnily enough, flashing TWRP*allowed me to boot into CYM again. Activated USB*Debugging and allowed the Host to connect, but still no luck in TWRP.
But since I*had access again I* just copied the Guru image over USB*to the Sdcard, booted back into TWRP*and installed the ROM*manually.
Stock recovery = yes
Stock radio = yes
Root = No
You will now have full stock Rom and recovery. Reboot the device and go to settings>about>Software Updates. Download and install the OTA update. Repeat process untill your on JB 3.xx.401.x firmware.
Click to expand...
Click to collapse
219486214 reboots later... JB*3.62.401.1, hooray!
Then use rumrunner to gain s-off. :good:
Click to expand...
Click to collapse
Another adventure... In the official instructions it says unlocked OR*rooted, so I*did not bother with rooting.
rumrunner then failed and damaged Recovery leading to not being able to boot into TWRP*and thus being unable to install SuperSu zip.
Had to reflash recovery, install SuperSu and run rumrunner again... Which again failed (becuase the screen was off, I did not see that ADB*Shell requested root).
After a couple of tries now it worked ^_^
Thanks a lot for your explanations.
Now I just have to find out how to get to Firmware 5.0.2 to install the latest ViperOne.
Edit:*When I try to run the OTA*update to 4.19.401.11 it just boots into Recovery
Hoelli169 said:
Worked!
This didn't work. While in TWRP, adb was not able to connect. Funnily enough, flashing TWRP*allowed me to boot into CYM again. Activated USB*Debugging and allowed the Host to connect, but still no luck in TWRP.
But since I*had access again I* just copied the Guru image over USB*to the Sdcard, booted back into TWRP*and installed the ROM*manually.
219486214 reboots later... JB*3.62.401.1, hooray!
Another adventure... In the official instructions it says unlocked OR*rooted, so I*did not bother with rooting.
rumrunner then failed and damaged Recovery leading to not being able to boot into TWRP*and thus being unable to install SuperSu zip.
Had to reflash recovery, install SuperSu and run rumrunner again... Which again failed (becuase the screen was off, I did not see that ADB*Shell requested root).
After a couple of tries now it worked ^_^
Thanks a lot for your explanations.
Now I just have to find out how to get to Firmware 5.0.2 to install the latest ViperOne.
Edit:*When I try to run the OTA*update to 4.19.401.11 it just boots into Recovery
Click to expand...
Click to collapse
You need stock rom and recovery to install OTA updates. You can just flash the rom again with stock recovery to take further OTAs.
But as your now s-off you can just flash the firmware manually. You don't need to re lock the bootloader again. That's only for s-on users.
You can download the rest of the firmware updates here https://www.androidfilehost.com/?w=files&flid=32777
You must flash at least one zip for each firmware version. I.e if your on 3.xx.401.x then you have to flash
4.xx.401.x
5.xx.401.x
6.xx.401.x
7.xx.401.x
Then you can flash twrp and install a lollipop rom. You should have the rom on the internal storage before you start as the device won't boot after flashing the firmware as it will replace the stock boot.img. So you will need to flash a rom before it will boot. :good:
Commands for flashing the firmware zip as follows.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip "name-of-firmware".zip
fastboot flash zip "name-of-firmware".zip
fastboot reboot-bootloader
Flash TWRP, Install Rom, Done :good:
Sent from my SM-T230 using Tapatalk
Danny201281 said:
You need stock tom and recovery to install OTA updates. You can just flash the rom again with stock recovery to take further OTAs.
But as your now s-off you can just flash the firmware manually. You don't need to re lock the bootloader again. That's only for s-on users.
You can download the rest of the firmware updates here
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
I thought I had to adhere to some upgrade path when handling firmwares but if that's not the case I'll be happy to use the latest, thanks!
Hoelli169 said:
I thought I had to adhere to some upgrade path when handling firmwares but if that's not the case I'll be happy to use the latest, thanks!
Click to expand...
Click to collapse
See my edited post above. You can't just flash the latest firmware. It might work but there's a risk of bricking your phone if you skip firmware versions
Sent from my SM-T230 using Tapatalk
Danny201281 said:
See my edited post above. You can't just flash the latest firmware. It might work but there's a risk of bricking your phone if you skip firmware versions
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
Ahh yes. Well, another interesting one going through the firmware updates. Going from 5.xx to 6.xx nearly killed my phone. Screen went black no matter how long I*pressed the power button and connecting through USB*mounted some strange folders on the device.
Luckily found Dexter's thread and his unbricking script solved the problem:
http://forum.xda-developers.com/showthread.php?t=2770684
Now ViperOne is updating, yay ^__^
Hoelli169 said:
Ahh yes. Well, another interesting one going through the firmware updates. Going from 5.xx to 6.xx nearly killed my phone. Screen went black no matter how long I*pressed the power button and connecting through USB*mounted some strange folders on the device.
Luckily found Dexter's thread and his unbricking script solved the problem:
http://forum.xda-developers.com/showthread.php?t=2770684
Now ViperOne is updating, yay ^__^
Click to expand...
Click to collapse
[emoji28] few!! Yeah firmware can be tricky. Glad you got it sorted though. Dexter's thread is a life saver. . Enjoy lollipop :good:
Sent from my SM-T230 using Tapatalk