I previously asked if there was a Deodexed stock ICS rom for my Galaxy Tab 7 plus t869, and received no response.
So I decided to try to learn how to Deodex the stock rom myself and found this tutorial
http://forum.xda-developers.com/showthread.php?t=1835900
After following the tutorial, including Copying and pasting the ADB comands directly from the tutorial, I rebooted into the CWM recovery and cleared the cache, Dalvic cache, and did a factory reset.
When I rebooted the tablet, it stayed on the flashing Samsung logo, for over 45 minutes. So I would call that a Bricked tablet
Is there something I did wrong?
Is there a different set of commands that I should use based on my Tablet model?
I know I am going to have to re-flash the rom with Odin, but I would like to try to get to the bottom of this Deodexing thing, since it is the only way I am going to get one for the stock ICS rom.
Any help you can offer would be appreciated.
misternest said:
I previously asked if there was a Deodexed stock ICS rom for my Galaxy Tab 7 plus t869, and received no response.
So I decided to try to learn how to Deodex the stock rom myself and found this tutorial
http://forum.xda-developers.com/showthread.php?t=1835900
After following the tutorial, including Copying and pasting the ADB comands directly from the tutorial, I rebooted into the CWM recovery and cleared the cache, Dalvic cache, and did a factory reset.
When I rebooted the tablet, it stayed on the flashing Samsung logo, for over 45 minutes. So I would call that a Bricked tablet
Is there something I did wrong?
Is there a different set of commands that I should use based on my Tablet model?
I know I am going to have to re-flash the rom with Odin, but I would like to try to get to the bottom of this Deodexing thing, since it is the only way I am going to get one for the stock ICS rom.
Any help you can offer would be appreciated.
Click to expand...
Click to collapse
For problem bootloop :
HTML:
adb devices adb reboot
For deodexed rom : http://forum.xda-developers.com/showthread.php?t=1598829
devid801 said:
For problem bootloop :
HTML:
adb devices adb reboot
For deodexed rom : http://forum.xda-developers.com/showthread.php?t=1598829
Click to expand...
Click to collapse
Hi, thank you for replying.
I have tried the adb command you posted and unfortunately it did not work.
{
"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"
}
My tablet is still stuck on the Samsung logo.
I also looked over the topic you linked to and it is just a theme tutorial for deodexed roms, there is no deodexing tutorial or link to a deodexed rom there.
That 'adb reboot' -command only reboots the tab back to the boot loop and is essentially the same as keeping the power button down for about 15 seconds.
Firmware re-flash is probably only option to fix that boot loop.
Sent from my GT-P6210
miksumortti said:
That 'adb reboot' -command only reboots the tab back to the boot loop and is essentially the same as keeping the power button down for about 15 seconds.
Firmware re-flash is probably only option to fix that boot loop.
Sent from my GT-P6210
Click to expand...
Click to collapse
comand
HTML:
adb devices
found devices
comand
HTML:
adb reboot
If you persist botloop flash with odin stock rom samsung..
edit: unnecessary post..
Related
im doing the combination
and when i enter i get like a dead android with a red triangle
Did you happen to root and install a non-stock recovery?
Is this an OTA update that downloaded, or did you download it yourself?
Did you download the correct version (WW, TB, JP, US, CN, DE, etc.)?
That sounds like the stock recovery to me. I think you just need something to flash.
sent from my transformer
I have recently discovered that I am unable to boot into recovery. It fails to load with the red triangle. I am completely stock too.
I have tried manually updating the latest firmware via SD. I also tried renaming the update to EP101_SDUPDATE.zip & booting into recovery. My transformer does up date but I still cannot boot into recovery. Any suggestions?
jadesse said:
I have recently discovered that I am unable to boot into recovery. It fails to load with the red triangle. I am completely stock too.
I have tried manually updating the latest firmware via SD. I also tried renaming the update to EP101_SDUPDATE.zip & booting into recovery. My transformer does up date but I still cannot boot into recovery. Any suggestions?
Click to expand...
Click to collapse
you are in recovery, stock recovery. if you want cwm recovery you have to root and install cwm recovery
That sounds exactly like the stock recovery to me. The stock recovery is fairly plain. If you want fireworks and fanfare, you'll have to flash a custom recovery. Search the dev section for how-to threads. Also note that some recoveries use the internal sd card.
sent from my transformer
No guys its actually a problem that recently happened to me too. Asus messed something up with an ota update. I know what stock recovery looks like and our problem is actually a dead android picture with red caution triangle instead of recovery.
Does it look like this?
{
"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"
}
mackdaddy187 said:
No guys its actually a problem that recently happened to me too. Asus messed something up with an ota update. I know what stock recovery looks like and our problem is actually a dead android picture with red caution triangle instead of recovery.
Click to expand...
Click to collapse
The look of the stock recovery has changed a few times already. Jadess posted above that it took and updated a stock firmware so that's your stock recovery.
If it doesn't detect any "update" file you get the triangle with the ! as down in pictures above
Guys, use gnufabio's recovery installer to fix the issue.
+1 Gnufabio's recovery installer, you have stock.
Never use ROM manager on the TF, it's good on supported phones but causes problems here.
Team Rouge's recovery (one I use) also has an NvFlash version if you're Sbkv1
Hi guys,
I just tried to revert my nexus 5 to stock. I was running the stock rom with a custom kernel which caused a lot of lag issues for me.
What I did: fully wiped the device in TWRP and afterwards I let the Nexus Root Toolkit download and install the default 4.4.2 factory image. (flash stock + unroot)
However, during the process, it stucks at erasing userdata.
{
"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"
}
So afterwards, I decided to plug the device out and let it reboot. However, stucks at the bootanimation.
I am however able to boot into the bootloader and do the flashstock process again. Time after time it stucks at erasing userdata. Is this the final step of the process? the system is flashed to in theory it should be able to boot. When I try to boot into the recovery, it shows a 'dead' android.
Can someone please tell me what to do? I might have wiped the internal memory in TWRP which might be the cause.
sjondenon said:
Hi guys,
I just tried to revert my nexus 5 to stock. I was running the stock rom with a custom kernel which caused a lot of lag issues for me.
What I did: fully wiped the device in TWRP and afterwards I let the Nexus Root Toolkit download and install the default 4.4.2 factory image. (flash stock + unroot)
However, during the process, it stucks at erasing userdata.
So afterwards, I decided to plug the device out and let it reboot. However, stucks at the bootanimation.
I am however able to boot into the bootloader and do the flashstock process again. Time after time it stucks at erasing userdata.
Can someone please tell me what to do? I might have wiped the internal memory in TWRP which might be the cause.
Click to expand...
Click to collapse
Use a USB 2 port. USB 3 doesn't work well with adb.
aooga said:
Use a USB 2 port. USB 3 doesn't work well with adb.
Click to expand...
Click to collapse
I gave my usb 2 port a try and now it has finished flashing. THANK YOU VERY MUCH
sjondenon said:
I gave my usb 2 port a try and now it has finished flashing. THANK YOU VERY MUCH
Click to expand...
Click to collapse
No problem. Just remember that for next time
I was gone for 3 days, left my N8000 charging while on Gnabo ROM V4 while I was gone. When I got home the tablet was working fine, unplugged it from the charger. (not sure if related to problem)
I did not look at it after plugging it out but some hours later I came back to discover it turned itself off. I tried turning it on but it was stuck on the glowing Samsung bootanim. Eventually it would automatically go into recovery but do nothing at all.
I repartitioned with http://forum.xda-developers.com/showthread.php?t=2363703 N8000 4.0.4 PIT file, Nand erased all, and flashed KIES_HOME_N8000XXALGA_N8000OXAALGA_861995_REV00_user_low_ship (4.0.4 Germany Stock Firmware) through odin.
When powering on, it is still stuck on the glowing Samsung bootanim. /efs still doesn't mount in stock or twrp recovery. When powering the device off through twrp and charging from stock charger a battery with timer inside shows but doesn't change. Even after unplugging the cable, "charging initialization" stays with screen on.
Please help, I do not have /efs or PIT backups.
Recovery after firmware+repart: (wiping data/factory resetting got rid of /data mount error)
{
"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"
}
I got it to boot now, steps taken:
1. Flashed KIES_HOME_N8000XXALGA_N8000OXAALGA_861995_REV00_user_low_ship (4.0.4 Germany Stock Firmware(Get your own from sammobile, this might be country specific(germany fw also goes for belgium))) + repartition with http://forum.xda-developers.com/showthread.php?t=2363703 N8000 4.0.4 PIT file
2. Flashed both again but with repartition unticked and Bootloader Update ticked.
3. Wipe data/factory reset + wipe cache in recovery and reboot.
Progress: (no baseband, no IMEI, need modem/phone flash) still unable to mount /efs in recovery
Now I just need efs backup from someone, I think...
When you flash, does it flash alright? or does it give an error? I'm asking cause i have the same problem but I'm stuck at flashing anything!
ayeladawy said:
When you flash, does it flash alright? or does it give an error? I'm asking cause i have the same problem but I'm stuck at flashing anything!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1944858 post 6 it was working for me. I had same problem and it fix!:good:
Panayiotis said:
http://forum.xda-developers.com/showthread.php?t=1944858 post 6 it was working for me. I had same problem and it fix!:good:
Click to expand...
Click to collapse
It says error mounting system.
Hi,
I was running the latest stock Android 8 firmware for the op6 with magisk & twrp.
I delayed the firmware update since month then yesterday I was forced to update.
My phone reboot everything was fine. no twrp & no root anymore because of the update.
I booted in latest twrp (fastboot boot twrp.img....) then I flashed the twrp.zip. After reboot I flashed magisk.zip.
After the latest reboot phone stuck for ~30 sec at the warning message saying boot-loader unlock blablalbla. then the phone reboot again and put me in twrp.
What can I do from there ?
Thanks for you help.
Julian.
Do I need to use this method to start from scratch ?
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
You have used the latest blue spark TWRP? If not you should do it
Try booting to the other slot
Deacon-Frost said:
You have used the latest blue spark TWRP? If not you should do it
Click to expand...
Click to collapse
I installed the last twrp on official website its not the one ?
I manage to boot the OS with a factory reset on twrp but I lost all my apps. only magisk app what installed. (because it was installed as a system app?)
I flashed the zip again and now it's everything is working but I can't install netflix... so it seems I'm not systemless :/
if you have any idea on how to make all the things right again it will be nice :good:
thanks for you help
foomanjackel said:
Try booting to the other slot
Click to expand...
Click to collapse
I'm still struggling with this A & B. last time I was on twrp it show me I was on B I think
you need to flash two times the full rom, flash rom flash twrp reboot to twrp, flash rom flash twrp, reboot to twrp flash magisk, reboot
Toni Moon said:
you need to flash two times the full rom, flash rom flash twrp reboot to twrp, flash rom flash twrp, reboot to twrp flash magisk, reboot
Click to expand...
Click to collapse
two time like on A and on B ?
how to boot A to B or B to A ?
when you flash one time and reboot to recovery and flash the rom again,you flash the rom in two slots, you didn't need change slots
I had the same problem, boot loops after rooting the recent OTA update. after soem troubleshooting with TWRP and not really getting anywhere I accidentally wiped the phone (stuck in the Chinese menus, was a mistake). prolly for the best, working great after re-flashing the OTA.
Toni Moon said:
when you flash one time and reboot to recovery and flash the rom again,you flash the rom in two slots, you didn't need change slots
Click to expand...
Click to collapse
Understood !
When I flash magisk for the last step do I need to swipe right "to allow modification"? if I want to be systemless?
A guy is talking about that here and I'm confuse about that => https://forum.xda-developers.com/showpost.php?p=76564294&postcount=6
{
"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"
}
I unlocked my phone, installed TWRP through fastboot, booted recovery, wiped and installed LineageOS. System didnt wanted to boot up so I went back to recovery where I wanted to wipe all and try installing again.
TWRP didn't saw my internal storage. I didnt know what to do, so I decided to download MiFlash and install stock rom, but I got error: "error:Sending sparse 'userdata' 1/3 (740908 KB) FAILED (Error reading sparsefile)" and now my phone boots to fasboot mode.
When I try to go recovery I get stock recovery. Is there anyway to revive my phone? It's m2101j20sg model.
crashykk said:
I unlocked my phone, installed TWRP through fastboot, booted recovery, wiped and installed LineageOS. System didnt wanted to boot up so I went back to recovery where I wanted to wipe all and try installing again.
TWRP didn't saw my internal storage. I didnt know what to do, so I decided to download MiFlash and install stock rom, but I got error: "error:Sending sparse 'userdata' 1/3 (740908 KB) FAILED (Error reading sparsefile)" and now my phone boots to fasboot mode.
When I try to go recovery I get stock recovery. Is there anyway to revive my phone? It's m2101j20sg model.
Click to expand...
Click to collapse
Reboot your phone and observe on the top part of the phone while there is the POCO logo showing.
1) If there is an unlocked lock icon on the top, you should be able to rescue with TWRP.
{
"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"
}
Type the fastboot code to get to TWRP again so you can flash ROMs.
Read here for ROM flashing tutorial.
https://forum.xda-developers.com/t/4288121/post-85137963
Step 16 is a must.
2) If you did not see this icon during booting POCO logo, chances are you accidently locked your bootloader with MiFlash. In this case, find Xiaomi repair center for warranty support.
I know how to flash a rom, but TWRP does not see my internal storage. Like it wasnt there.
edit:
I flashed Orangefox recovery and it did the trick. I was able to place some rom on internal storage and install it, but now i have 12 gb of storage instead of 233gb?
edit:2
I formated data and it went back to normal. Now i have my 256gb back.
I think you were encrypted, please read more online and follow rom flashing instructions. You didn't follow it that's why you were in trouble.
I flashed, rooted, unbricked a lot phones back in the Samsung S6 days. Even Redmi Note 5 Pro from xiaomi, but never heard of something like rom encrypting your access in recovery.
I didnt flashed custom roms on my Samsung s8 and s9, cuz they had fine software. MIUI 12 is so bad that I considered selling that Poco.
You didn't follow instructions, TWRP works perfectly fine. And the step you missed is Formatting Data partition after flashing ROM which decrypts it. (thus why you couldn't access internal storage or boot)
And you will run into same issue with OrangeFox aswell if you do the same mistake. Flashing procedure is a lot different in new smartphones.
I didn't follow, cuz I didn't know that flashing procedure is a lot different in new smartphones. I looked at it, it looked very similar, so I went with old habits. Now I know what to expect.