Hi,
for no reason my I/O tab 10.1 started boot looping.
Basically I need the orginal boot, recovery and system.img files for the Google I/O tab 10.1
All the ones I've found so far are rooted or don't even boot.
Basically looking for the clean stock i/o images.
Many thanks
http://droidbasement.com/galaxy/
which of these should I use?
bump bump. anyone?
Related
Since I was stupid enough to flash the wrong version of a the metro ui theme for the galaxy tab 10.1, I'm now stuck in a boot loop. The only issue is that I don't have a nandroid back up on the tab itself, it's on my pc. Another issue is that the zip file of my rom also isn't in my tablet storage, as the developers only way to fix boot loop issues was to flash the rom you had. Anyone have any ideas of what I can do? I can't mount as a usb storage in cwm v5.1 as i get the "unable to open ums lunfile" error.
Go into download mode and Odin back to stock is all I can think of. Or Odin a different version of CWM
thank god for odin
Sent from a Gtab 10.1 running Build 30
I wanted to flash a new rom on my tablet but it got to the ASUS logo then it boot loops. I have tried to restore my Nandroid but it get's to the ASUS logo and then boot loops.
Is the tablet broken or can I fix it?
EDIT: I forgot to delete a old rom and tried to flash it and got the tablet to boot. I wanted to try the AOKP rom that clocks to 1.7 GHz but I think it klocks it to 1.7 GHz when you flash the rom maby that's what ****ed it up?
If you use CWM, flash TWRP 2.2.2, CWM is always causing such problems (I had them once too and am now on TWRP 2.2.2 for a long time without problems...)
Did you get this problem figured out or do you still have issues?
Hi, today i just played with file systems today and now i can't install any other roms excepting supermanrom. So i think i have a problem with file systems. Which file system does s7 edge using for default? Can any master help me? After im installing any rom it's stuck at bootloop
Which one should i use for example system and data file? ext4 or f2fs or any other?
Can you give us some more information?
if your stuck in boot loop? can you not boot into twrp?
Did you turn off OEM unlocking in developer options?
If you can load twrp? lots of info on returning to stock on here
just use search for installing to stock after bad flash.
Or other option would be flash another custom Rom.
Or are you saying you cant do any of the above?
If so what errors are you getting? it may help others that know more on
returning to stock.
I only flashed my first Rom to my S7E a few days ago after two bad flashing and had to have phone fixed in shop
to be honest I just did not read every thing and missed out apart and got stuck in boot loop.
but this time did the same but had twrp installed and just kept reading up on errors i was getting and in the end
i got it sorted.
May not of been much help but hope you get it sorted.
Good Luck
leggoman said:
Can you give us some more information?
if your stuck in boot loop? can you not boot into twrp?
Did you turn off OEM unlocking in developer options?
If you can load twrp? lots of info on returning to stock on here
just use search for installing to stock after bad flash.
Or other option would be flash another custom Rom.
Or are you saying you cant do any of the above?
If so what errors are you getting? it may help others that know more on
returning to stock.
I only flashed my first Rom to my S7E a few days ago after two bad flashing and had to have phone fixed in shop
to be honest I just did not read every thing and missed out apart and got stuck in boot loop.
but this time did the same but had twrp installed and just kept reading up on errors i was getting and in the end
i got it sorted.
May not of been much help but hope you get it sorted.
Good Luck
Click to expand...
Click to collapse
I can boot into twrp but i cant flash stock frimware with odin. It's giving FAIL error to me immidietly when im trying to do. And yes, OEM was open before
Now i flashed stock rom via odin, but when i install twrp again on my device it stucking at boot loop. Why?
Then i realized something that whatever i flash something via odin or something else, its stucking at bootloop
sdiown said:
Hi, today i just played with file systems today and now i can't install any other roms excepting supermanrom. So i think i have a problem with file systems. Which file system does s7 edge using for default? Can any master help me? After im installing any rom it's stuck at bootloop
Which one should i use for example system and data file? ext4 or f2fs or any other?
Click to expand...
Click to collapse
Format all with ext4 (in twrp). Especially the system. Because all touchwiz cusrom can only run on ext4. After all normal, you can just format to f2fs for data and cache
Hello All,
Thank you for taking time reading this post. My buddy tried to install some custom ROM through Oden and he ticked the Nand Erase during the flash. Now the tab wont go past the boot screen. I tried flashing Stock ROM and some PIT file I found online through Oden, but still no use. I guess the device partitions are gone. Could some please kindly help me how to fix this. I have downloaded stock ROM from this site. and also tried wiping cache/resetting to factory.
The device can go into update/recovery at boot, so It must be soft brick. I hope.
Thank you,
Hey, I'm new here when it comes to writing forum posts, so bare with me.
I've had this tablet for a few years now and I had flashed it with one of Magendanz roms (Nexus Stock) and I wanted to change to the LineageOS rom he had. I downloaded the .zip file and copied it to my sdcard and tried to get into TWRP to flash it. I did restart to recovery in the OS and once it restarted, it's been doing a boot loop ever since. I have tried using Odin to flash the rom that way, but for some reason it'll keep doing a boot loop after it's done flashing and restart. I can try going back to the stock firmware if it's a final option to get this tablet working again, but I would love to see if I can get LineageOS to work.
DengekiMatsuko said:
I did restart to recovery in the OS and once it restarted, it's been doing a boot loop ever since.
Click to expand...
Click to collapse
I had a similar issue once. It turned out that after flashing, not all the partitions mounted properly.
Are you still using TWRP? Boot to recovery, and go into "Mount". Make sure the system and other partitions are actually ticked. That solved the problem for me, and I was able to successfully boot to the system.
Hopefully your issue is that simple!
I managed to brick my Tab A 10.1 (2019) last year by dirty flashing ROMs I shouldn't have. I properly munted it, I couldn't even get into recovery. But I could still get into download mode with a USB cable plugged in to my laptop (it needed to be plugged in for download mode to come up). I flashed the stock ROM, which made it bootable again, which then allowed me to re-flash TWRP and then Magendanz' LOS18.1 ROM.
If you completely break your tablet, reflashing the latest stock ROM for your region is a great way to get back to a familiar starting point. You can then follow people's guides online to get where you want to be.