Database Info

[Q] Help Flashed custom rom with s-on with no backup

hi
I've tried to downgrade my HTC EVO 3D GSM HBoot 1.49.0018 but not successfully, and then I have flashed a custom ROM with s-on without backup with the result my phone was stcuk the boot screen.
so I searched for some threads so I could fix it with the home screen and I found one where I should
Wipe data / factory reset
Wipe cache partition
Wipe Dalvik Cache
format / system
format / data
format / cache
install custom rom from sd card
reboot
so now I'm stuck with a custom rom unlocked pre s-on phone
is there any way it can be fixed
I would like to have full root and s-off
Yes im a noob but if you dont try you never lern

Can you get into recovery?If yes reboot in to recovery and connect your phone to pc follow this:
Download AlphaRevX and extract the files to a folder. (A form will show up on the download page, keep it opened.)
Connect your device to the system and run Aplharev.exe.
You will be asked to enter a Beta key at this stage. Simple copy the serial number that shows up in the brackets in the prompt as shown in the screenshot above, and paste it into the form on the download page.
Hit the Generate Key on that form and once you have the key, enter it into the prompt to see a Beta key accepted message.
The application will start the S-Off procedure and should complete in around 90 seconds. Incase it does not start, wait fro around 15 minutes and re-do the whole process.
This might require debugging ticked earlier and knowledge of adb.Not sure it will work or not because I dont own a htc device and havent been in a situation like this.I'm not responsible if anything happens.But trying doesnt affect though.

Thx but it will not help because there is that I must choose hboot but I have not some of them listed 1.49.00007 and 1.49.00008 and i have 1.49.00018 then I have to downgrade more ideas im open for everything

[Q]HTC Desire S Stopped at White HTC Log After Flashing

Hi Friends,
I yesterday tried to flash my Desire S but now i have faced a huge problem.It shows and stopped in HTC log.
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Here i flashed with clockwork mode recovery.
Rooted using:su-3.0.5-efgh-signed.zip
and finally installed CWM v5.0.2.0.There i successfully fully backed up current ROM too.So far everything was fine and now started the scary part.
after that i downloaded MIUI.us_saga_v4_2.11.9_Eng_Deo_ZipA_Signed.zip and flashed with it.Everything went fine and no errors found and i kept whole night assuming it
would take time to get booted up.But i felt some thing is wrong and tried to restore my initial rom back up via CWM.But it restored with no erros but still stopped with HTC logo.
I did wipe date/factory reset,wipe cache partition, and wipe Dalvik cache and flashed CM 7.2 even result is same.And now i cant run adb where it shows no devices in fast-boot screen.
I feel i did a mistake by not using the boot.img in rom. isn't?Further any idea to make my back up work?

codefreaker00 said:
Hi Friends,
I yesterday tried to flash my Desire S but now i have faced a huge problem.It shows and stopped in HTC log.
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Here i flashed with clockwork mode recovery.
Rooted using:su-3.0.5-efgh-signed.zip
and finally installed CWM v5.0.2.0.There i successfully fully backed up current ROM too.So far everything was fine and now started the scary part.
after that i downloaded MIUI.us_saga_v4_2.11.9_Eng_Deo_ZipA_Signed.zip and flashed with it.Everything went fine and no errors found and i kept whole night assuming it
would take time to get booted up.But i felt some thing is wrong and tried to restore my initial rom back up via CWM.But it restored with no erros but still stopped with HTC logo.
I did wipe date/factory reset,wipe cache partition, and wipe Dalvik cache and flashed CM 7.2 even result is same.And now i cant run adb where it shows no devices in fast-boot screen.
I feel i did a mistake by not using the boot.img in rom. isn't?Further any idea to make my back up work?
Click to expand...
Click to collapse
used to had that kind of problem...i had to pulled out battery, power + volume button to enter recovery....in recovery re-install the backup......(note: pulling battery is very dangerous as mention everywhere here)

That was a mistake, yes. But if you haven't flashed any boot.img since rooting your phone, I would have expected restoring the backup should have worked.
Or have you flashed a boot.img in between?

1. extract "boot.img" from inside the zip file of the ROM.
2. install the ROM
3. reboot into bootloader and goto fastboot
4. in your PC's command prompt run "fastboot flash boot boot.img"
check this for help http://forum.xda-developers.com/showthread.php?t=1525100

I'm wondering, how many more threads like this can a forum tolerate. At any given time there are 2 threads like that on the front page of the forum. WTF? Should be THE most asked question since HTC released bootloader unlock - and people didn't learn to read/search yet.
FASTBOOT FLASH BOOT BOOT.IMG
Yes, that includes restoring from backups too. If you read that recovery can't flash kernels - it means IT CAN'T EVER FLASH ANY KERNEL FROM ANYWHERE.

[6045Y] Idol 3 won't go into fastboot or recovery

Hi, today I wanted to restore a twrp backup (in order to unroot and get the OTAs updates) posted there : http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745, the Model: 6045Y(Europe) Firmware: 5.0.2-010 05 (my idol 3 is the 6045Y).
I wiped everything but OTG and external sd.
I first restored the system image and then the boot because there are 2 files with this backup.
My idol 3 now just boots fine, but every 4-5 minutes, depending on how hard I am using it, it reboots to system.
When I try to boot in fastboot mode with adb reboot fastboot, it doesn't work and shows a black screen. When I press vol up + power, it goes into a kind of "recovery" (don't know if it's the right name of this mode, but there are a lot of options like wipe data, cache, install update with adb and it seems to be stock) (I precise I tried to factory reset/wipe data multiple times and it didn't solve my problem).
When I try to go into recovery, it does the same thing except it never reboots (I can only factory reset/wipe via the "recovery I told you about up there).
On my SD I have 3 working twrp backups which I could restore if i could access the option to.
What I would need to do to solve my problem is, I guess, figure out how to access my recovery (which should still be installed) or how to boot on it with adb on my computer, and then restore one of the twrp backups on my SD which are working.
If you know how to do that or just how to solve this reboot problem, please answer the thread. Thanks in advance.

T0mSIlver said:
Hi, today I wanted to restore a twrp backup (in order to unroot and get the OTAs updates) posted there : http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745, the Model: 6045Y(Europe) Firmware: 5.0.2-010 05 (my idol 3 is the 6045Y).
I wiped everything but OTG and external sd.
I first restored the system image and then the boot because there are 2 files with this backup.
My idol 3 now just boots fine, but every 4-5 minutes, depending on how hard I am using it, it reboots to system.
When I try to boot in fastboot mode with adb reboot fastboot, it doesn't work and shows a black screen. When I press vol up + power, it goes into a kind of "recovery" (don't know if it's the right name of this mode, but there are a lot of options like wipe data, cache, install update with adb and it seems to be stock) (I precise I tried to factory reset/wipe data multiple times and it didn't solve my problem).
When I try to go into recovery, it does the same thing except it never reboots (I can only factory reset/wipe via the "recovery I told you about up there).
On my SD I have 3 working twrp backups which I could restore if i could access the option to.
What I would need to do to solve my problem is, I guess, figure out how to access my recovery (which should still be installed) or how to boot on it with adb on my computer, and then restore one of the twrp backups on my SD which are working.
If you know how to do that or just how to solve this reboot problem, please answer the thread. Thanks in advance.
Click to expand...
Click to collapse
The correct adb commands are
Code:
adb reboot bootloader
or
Code:
adb reboot-bootloader
and from there you should be able to boot the TWRP image with
Code:
fastboot -i 0x1bbb boot <recovery image filename>

[OP7][10.0.3.GM57AA] (GM1900) Cannot boot system, stays in fastboot

Hey Folks,
been lurking the forums for long, thanks to your help always found a solution to my troubles / needs. Now I am somewhat stuck, and don't want to mess up any further:
I just got my OP7 (was on a OP1 since 2015), and did the following:
Root, following this tutorial: youtu.be/R_5BTxJBAOs (not allowed to post links yet...)
Update to 10.0.3 following this tutorial: youtu.be/ytp1w0ak3io (still not allowed to post links)
Happily configured new phone for 2 days
Disabled superuser in Magisk (was that the mistake?)
Rebooted directly into Recovery (planning to perform backup with TWRP)
TWRP comes to life, does not let me backup, says it cannot access /data
now I am unfortunately left with this behaviour:
Boot into Fastboot works
Boot into recovery (TWRP) works
Boot into system throws me back into fastboot
Access via adb / fastboot from PC works
Coming from a OP1 this is the first time for me working with TWRP / Magisk / Fastboot and that sort, so I am somewhat lost on how to proceed.
Could you please advise?
Your help is much apprechiated!
Update:
I was able to Wipe /data through TWRP and am now back on 957 after boot from Slot A. Slot B is still unable to boot system.
Going back to TWRP after initial setup I am now again prompted for the PIN to decrypt. Didn't do that before the wipe. That brings me to the assumption that /data was somehow corrupted. Any guesses?

schaich42 said:
Hey Folks,
been lurking the forums for long, thanks to your help always found a solution to my troubles / needs. Now I am somewhat stuck, and don't want to mess up any further:
I just got my OP7 (was on a OP1 since 2015), and did the following:
Root, following this tutorial: youtu.be/R_5BTxJBAOs (not allowed to post links yet...)
Update to 10.0.3 following this tutorial: youtu.be/ytp1w0ak3io (still not allowed to post links)
Happily configured new phone for 2 days
Disabled superuser in Magisk (was that the mistake?)
Rebooted directly into Recovery (planning to perform backup with TWRP)
TWRP comes to life, does not let me backup, says it cannot access /data
now I am unfortunately left with this behaviour:
Boot into Fastboot works
Boot into recovery (TWRP) works
Boot into system throws me back into fastboot
Access via adb / fastboot from PC works
Coming from a OP1 this is the first time for me working with TWRP / Magisk / Fastboot and that sort, so I am somewhat lost on how to proceed.
Could you please advise?
Your help is much apprechiated!
Update:
I was able to Wipe /data through TWRP and am now back on 957 after boot from Slot A. Slot B is still unable to boot system.
Going back to TWRP after initial setup I am now again prompted for the PIN to decrypt. Didn't do that before the wipe. That brings me to the assumption that /data was somehow corrupted. Any guesses?
Click to expand...
Click to collapse
You may have to install firmware through all in one tool. and the reason to ask pin is data is encrypted.

[Q] [Locked OP6] Bootloop after upgrading to 10.3.0 - how to recover without format

My dad got the OTA update to 10.3.0 on xmas day and installed it. However the phone is now stuck on boot logo. He has a locked phone just as it came out of the box (ie no TWRP, no OEM unlock, no root).
I am quite experienced with installing custom ROMs but with locked phones I am lost. Is there anyway to recover the device without deleting data / factory reset? This is because my dad has quite a lot of pics on the device that are not backed up (yeah I know...).
Things I've tried so far:
- reboot holding power button + volume up
- boot flash twrp from fastboot - no permission due to phone being locked
- in stock recovery I do not get access to device via cable
- installed Tool all in One - it sees phone via fastboot
I always use the Stock Fastboot ROMs for OnePlus 6 myself to recover from soft bricks but this wipes data so no option here. Unless there is a way to install parts of ROM? Any other tips or ideas from the awesome XDA community? :good:
Btw this is the update he installed:
Screenshot of update that was installed

If you boot on twrp, it does not ask for the pin code to access the data?
Maybe try the last twrp for OOS 10.3.0 : ( https://androidfilehost.com/?fid=4349826312261678088 )
Use command : fastboot flash boot twrp-3.3.1-16-enchilada-Q-mauronofrio.img
Try flash a new boot img :
Stock boot 10.3 img
https://drive.google.com/open?id=1w44cUg815g-H1h_6gObUVPLDTc_dtiMX

The phone is not unlocked and therefore has no TWRP recovery. This is my problem, if it was unlocked I would have figured out a way to fix it.
PS it does ask for pincode when accessing stock recovery

I'm not sure if this works on locked bootloaders but try switching boot slots using fastboot.

Couple of weird things:
-you don't need an unlocked bootloader for fastboot to boot back into the system
-the dual partition was designed precisely to prevent things like this from happening. When an update fails, you are supposed to roll back to the old slot you were on previously.
Anyway, since you are able to boot to fastboot, can you try to get to stock recovery again from fastboot and see if you can boot up to system from there?

Hey
You can try to change the boot slot using fastboot mode
It can help uh maybe
Its worth to try

awaiz said:
Hey
You can try to change the boot slot using fastboot mode
It can help uh maybe
Its worth to try
Click to expand...
Click to collapse
When I try to set it to slot A (it's B now) it says device does not support slots which is weird as 'fastboot getvar current-slot' does show it using slot B right now.
When I try to set it to B (ie current slot) it says: FAILED (remote: 'Slot Change is not allowed in Lock State').

awaiz said:
Anyway, since you are able to boot to fastboot, can you try to get to stock recovery again from fastboot and see if you can boot up to system from there?
Click to expand...
Click to collapse
When I reboot to stock recovery it gives two options:
- Wipe Data and Cache
- Advanced
There are two reboot options under Advanced:
1. Reboot to fastboot
2. Reboot to recovery
2nd option just boots it back to this same recovery. Boot to fastboot works as well. So there is no option to reboot the device.
Perhaps I can try to flash the stock ROM (kinda of dirty flash) but again not sure if that works on locked phone.

https://www.androidexplained.com/change-active-partition-slot/

JagDave said:
https://www.androidexplained.com/change-active-partition-slot/
Click to expand...
Click to collapse
This doesn't work unfortunately on a locked device.

I found the fix and it was very simple: in Recovery under Wipe Data and Cache it has the option to delete 1. System Settings 2. Cache 3. Wipe all (incl Data).
I choose option 1 (System Settings) and after that it booted and I had to set up phone again as with a new install but all data on sd card had remained. I did lose all apps but that is a very minor thing.
Thanks for everyone who thought along with me. We got there in the end

help me.. my op6 stuck in bootlogo.. how can i run my phone back. it is still locked never rooted..

Alamin4736 said:
help me.. my op6 stuck in bootlogo.. how can i run my phone back. it is still locked never rooted..
Click to expand...
Click to collapse
Bro..Use the Msm tool to get recover coz you have the locked bootloader

roel1976 said:
I found the fix and it was very simple: in Recovery under Wipe Data and Cache it has the option to delete 1. System Settings 2. Cache 3. Wipe all (incl Data).
I choose option 1 (System Settings) and after that it booted and I had to set up phone again as with a new install but all data on sd card had remained. I did lose all apps but that is a very minor thing.
Thanks for everyone who thought along with me. We got there in the end
Click to expand...
Click to collapse
I am facing similar problem with my OP5. When I boot in recovery, it asks for pattern to unlock. But does not accept any pattern. In the absence of pin, it gives option to Wipe Data. Will I get similar options like you did ? I am hoping to save my data.