Database Develop

Can't go any further then CWM recovery or download mode

I recenly tried restoring a froyo backup through CWM recovery and it resulted in this. It stays stuck in the I9000 logo screen and won't go any further. I've read that the bootloader might be corrupted and the only way is to flash a stock firmware and then reflashing whatever firmware I wanted to install....
Is this correct?
I AM able to go in either download mode AND recovery mode (v2.5.1.0) but no matter which firmware I want to flash ends up in "getprop" errors (Status 7)

dglaboi said:
I recenly tried restoring a froyo backup through CWM recovery and it resulted in this. It stays stuck in the I9000 logo screen and won't go any further. I've read that the bootloader might be corrupted and the only way is to flash a stock firmware and then reflashing whatever firmware I wanted to install....
Is this correct?
I AM able to go in either download mode AND recovery mode (v2.5.1.0) but no matter which firmware I want to flash ends up in "getprop" errors (Status 7)
Click to expand...
Click to collapse
use a recovery /rescue kit from My android collections link below, to get back booting also look at Quick solutions for insight

Ok I'll try them out and post back. thanx

Oh man....tried whole morning. Got some progress, it now boots (and bootloop) into the Galaxy boot animation whereas before it just got stock at the first I9000 screen. I already tried flashing a stock rom (XXJW4) but after reboot it gives me these errors:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------
update:
I managed to flash a rooted kernel and from CWM recovery I flashed a CM9 rom that I had on the sdcard.....
it flashed successfully and now I'm running CM9 stable version.
I should install gapps right to be able to use gmail app, market and other google apps??

XT1064 (Canada) - Difficulty flashing recovery.

Bought the xt1064 variant from Staples in Canada.
Device is unlocked. Upgraded to lollipop using this thread
Cannot flash recovery. Have tried Windroid tool as well as manually.
When trying to boot into recovery after failed attempt I just get the android with the open chest and an exclamation mark
I receive no errors when flashing recovery just the following text
Code:
cmd: getvar:partition-type:recovery
cmd: getvar:max-download-size
cmd: download:009e66000
cmd: flash:recovery

rb420 said:
Bought the xt1064 variant from Staples in Canada.
Device is unlocked. Upgraded to lollipop using this thread
Cannot flash recovery. Have tried Windroid tool as well as manually.
When trying to boot into recovery after failed attempt I just get the android with the open chest and an exclamation mark
I receive no errors when flashing recovery just the following text
Code:
cmd: getvar:partition-type:recovery
cmd: getvar:max-download-size
cmd: download:009e66000
cmd: flash:recovery
Click to expand...
Click to collapse
Use Flashify to flash TWRP 2.8.0.5 recovery. Its the easiest method

Duck86 said:
Use Flashify to flash TWRP 2.8.0.5 recovery. Its the easiest method
Click to expand...
Click to collapse
I've not gained root access yet.

rb420 said:
I've not gained root access yet.
Click to expand...
Click to collapse
Root the device before flashing recovery. Its always easier.
Follow this guide:
http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818

Duck86 said:
Root the device before flashing recovery. Its always easier.
Follow this guide:
http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818
Click to expand...
Click to collapse
Which one of these three do I choose for the xt1064?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rb420 said:
Which one of these three do I choose for the xt1064?
Click to expand...
Click to collapse
My apologies, I didn't read your post properly and didn't realise that you are on the XT1064, use this method to root instead, it is universal and will also flash a recovery for you
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862

Duck86 said:
My apologies, I didn't read your post properly and didn't realise that you are on the XT1064, use this method to root instead, it is universal and will also flash a recovery for you
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
Click to expand...
Click to collapse
Thanks so much. Got my Recovery installed.

rb420 said:
Thanks so much. Got my Recovery installed.
Click to expand...
Click to collapse
No problem! Glad to help

Stuck without an update

Hello,
Lately I've altered my system a bit and had to restore it to it's previous setup using pre-rooted boot.img and flashing back again "June08_NB1_v4.88B" OTA update. I've been on June update and this zip clearly for some unknown reason rolled me back into May secruity update.
Now whenever I try to update my device with auto updates back on into June or July it gives me this error message :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now I can't automatically get updates, but my attempts to use 4.88C which is July revision of security updates the recovery gives me a message that it's designed for 4.88B.
Now the question is - has somebody encountered a similar issue ? If so what can be done in this situation to get back automatic updates ?

Got it to work by wiping clean system, boot_a and boot_b.
Reflashed the stock paritions in their places from 4.88B with May security update.
My suspect in crime was busybox update that was installed system-wide directly into system & boot partitions which caused OTA mismatch and refusal of installation.

nice work done there.. hope it will help other people who are stuck too..
Sent from my Nokia 8 using XDA Labs

Hi,
Can you explain your method. I'm actually on 4.88B and I can't get no more security patch (still 1st may 2018).
Do you flash via fastboot (can you tell us the command lines)
Excuse my english

I've downlaoded both OTA and paritions zip. Flashed boot_a and boot_b using boot.img <fastboot flash boot_a boot.img; fastboot flash boot_b boot.img>
Then I did relock my OEM which resulted in a loopboot due to modified partitions, that's how I figured out to reflash OTA with update from SDCard using android stock recovery.

no unlocked bootloader, no flash.....
I hope an OTA in Android O with version higher than 4.88B....

Bricked Huawei P smart 2018 FIG-LX1 stuck in ERROR MODE

EDIT: I could fix this, if you have a device that works with HuRUpdater just download an update.zip, put that and the HuRUpdater zip in a new folder and it updates the recovery through TWRP so that's how I fixed it.
So I'm stuck in ERROR MODE. The only mode that works for me is Fastboot. I tried to reinstall recovery_ramdisk, system, cust and userdata but still in the same error. Before the brick EMUI 9.1 was installed. I've tried to install LineageOS 16 on my phone with TWRP, but I got error 7. First I've restored the nanddroid backup and I went stuck at a bootloop. I've entered eRecovery and downloaded the lastest version available on server and got this error. Any solutions for it? And the bootloader is unlocked, same with FRP. The error that shows in the screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is Func. NO: 11 (recovery image) and Error NO: 2 (load failed). Would be appreciated if someone answers.
Here is how Fastboot looks like...

I've had a similar situation which I got out of using advice from this forum. Basically, I erased data from fastboot, flashed the stock 9.1 recovery (which I found a link for in one of the P Smart ROM threads) and lineage boot.img.
I MAY also have powered on with BOTH volume keys pressed.
You do have fastboot access, so I'd guess you will eventually be able to recover via the stock recovery.

Another_Alchemist said:
I've had a similar situation which I got out of using advice from this forum. Basically, I erased data from fastboot, flashed the stock 9.1 recovery (which I found a link for in one of the P Smart ROM threads) and lineage boot.img.
I MAY also have powered on with BOTH volume keys pressed.
You do have fastboot access, so I'd guess you will eventually be able to recover via the stock recovery.
Click to expand...
Click to collapse
Thanks for the help but forget this, I could fix it, I'm gonna modify the thread to inform that I could solve it. I finally could access twrp via the 3 button update method and used HuRUpdater to update the recovery and could fix the phone with an EMUI 8 rom and recovery that I flashed with HuRUpdater. Also, I could install LineageOS without ERROR 7 by modifying a text file in the ROM zip. Thanks anyway.

LucastheBowser said:
Thanks for the help but forget this, I could fix it, I'm gonna modify the thread to inform that I could solve it. I finally could access twrp via the 3 button update method and used HuRUpdater to update the recovery and could fix the phone with an EMUI 8 rom and recovery that I flashed with HuRUpdater. Also, I could install LineageOS without ERROR 7 by modifying a text file in the ROM zip. Thanks anyway.
Click to expand...
Click to collapse
Hello! It seems Im having a same problem, since this device is somewhat discontinued by huawei, I cannot update it to any version, and cannot downgrade it either, using the "classic" sdcard method. Could you tell me how you used HuRupdater to flash the rom on yours?

The Solution for me->
Full package->
Software.rar
drive.google.com
Put your device on Testpoint mode:
Disconect the batery, join the point to gnd and conect usb cable on your pc.
and ..

and later you can update by SD

Question How to update or reflash stock samsung firmware if you are rooted?

I have rooted S21 ultra Exnos it has TWRP and decrypted what i want to ask is
If there is new firmware released which i want to update it then what is the procedure so that i can have my settings , root. and internal storage date? even TWRP
as device is decrypted if i flash the stock samsung firmware via ODIN then it will encrypt storage again right? which will format my internal storage as that is main thing... which i dont want and will overwrite the stock recovery also
please let me know options in comments

First, search for the ROM that you'd like and find out what suites you best yourself, that way you're more aware of the risks and what you actually need.
Second, flashing any ROM on decrypted device doesn't encrypt it again as long as you flash the decryption zip again like dm-verity, and flashing ROM with ODIN doesn't replace the recovery. You need to flash recovery through "AP" to do that.
Goodluck.

XDHx86 said:
First, search for the ROM that you'd like and find out what suites you best yourself, that way you're more aware of the risks and what you actually need.
Second, flashing any ROM on decrypted device doesn't encrypt it again as long as you flash the decryption zip again like dm-verity, and flashing ROM with ODIN doesn't replace the recovery. You need to flash recovery through "AP" to do that.
Goodluck.
Click to expand...
Click to collapse
i was talking about G998BXXU3AUF6 Samsung stock firmware which has 5 files total in ZIP but we need to flash 4 including AP
and i was not aware of that dm-verity zip will work in Samsung devices too as i decrypted it by the method which was mentioned in TWRP by command multi disabler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

nitinvaid said:
i was talking about G998BXXU3AUF6 Samsung stock firmware which has 5 files total in ZIP but we need to flash 4 including AP
and i was not aware of that dm-verity zip will work in Samsung devices too as i decrypted it by the method which was mentioned in TWRP by command multi disabler
View attachment 5353701
Click to expand...
Click to collapse
If you mean stock ROM you can get yours from sammobile it has whole archive of ROMs.
DM-Varity was just an example, you can use whatever works for you.
Also you can always just flash TWRP again. No biggie.