Hi Guys
I recently got a broken DELL Streak 5.
I actually tried many, many things with it and i have no idea what to try next.
Here is the list of things i did:
QDL and streakflash repairs (both successfully finished the operation)
flashing streakmod, clockworkmod and many stock recoveries
flashing lots of stock ROMs (pkg's)
Now what's the issue:
I got it in a condition where it was stuck on DELL logo (bootloop)
Streakmod and Clockworkmod both can't see the external SD card for some reason, they just write out an error "Cannot mount/read sdcard etc..."
The only combination that IS working is this particular stock firmware
version 203
build 6941
operator O2 21
release date Aug 5, 2010
It still says at the end of the flashing that it failed the flash but at the end it boots into the Android.
Any other recovery+pkg i flash (fastboot for recovery, sd card for pkg) will fail.
The 1xx recoveries are stuck at black screen, 3xx are just stucked up at the unmountable SD card or whatever.
I tried to switch the internal SD too, and succeeded but i still can run ONLY the 203 O2 firmware.
Does anyone have any idea why this is happening? I've tried everything i guess...
Thanks
Did you make sure that the recovery and the rom you want to flash match? Otherwise it will fail anyhow.
I did, i downloaded pkg and recovery from streak's wiki xda page and made sure they match before trying.
Related
Hi,
I ve done dozens of flashing with my Sony and Samsung phones with no problem. Today i decided to flash something fresh on my acer a500 tab. I did my first mistake Please help cause im reading threads for 3 hours now and i dont know how to proceed.
Heres the story:
I was on stock ics 4.0.3 rooted. I used successfully the AfterOTA tool and flashed Bootloader ics v3.14.8 + Recovery Ra v3.1.7 That gave me the Skrilacs Recovery V8.
Then i did all the usual wipes and flashed successfully RE-FLEX XX 40.4 Rom. After the first boot i noticed that my internal storage wasnt empty. It gave me only 14gb free. There were still stuff in like photos, some music and apps remainings. I desided to wipe again and reinstall the rom. I did it a couple of times and i got the same result (internal storage was still with the same stuff).
On my last try to install the rom again it stucked on rom booting screen (bootloop). I can still get into CWM but cant find a solution.
Thanks in advance for any help..
Update: just managed to get it boot back on stock. My heart is back to its place now.
Thanks
ok, I am using a GT-19505, root with CF-Auto-root, using TWRP recovery
the problem is, when I put a rom in sd card and try to flash it, it will usually says fail (I am sure I get the right version for my device, and I tried many different rom), no matter how many times I re-download the rom, it will says it failed. Even if it success (i.e. omega 7.1 rom), it got stuck in the boot screen forever. I tried to use odin to flash a stock rom, but it also got stuck in boot screen for half an hour before I pull battery.
so far the only successful flashing is a cyanogenmod nightly on 7/14 (I tried other days one, but they all failed to flash). I tried to restore that rom after attempt to flash another rom (omega 7.1), but find out it was factory reset after boot up. I got into the recovery and see that my data partition has 1016154 MB of stuff through the backup option.
I have no idea what had happen, and how to solve it, can someone help?
Hi guys
(SM-N9005)
So yesterday I had liquid smooth rom installed for the past month or so (I have been trying a variety of roms for the last year or so) and I was getting some bugs occuring and decided to put a new rom on.
I booted into recovery, did the normal backup, factory restore, clear cache and dalvik, installed the rom and restarted my phone. It then went into a boot loop.
At this point I assumed it was no biggy, so I just went back to recovery and chose to restore with the backup... except it wouldnt. it couldnt recognise the file it had just made.
So I then coppied some previous backups to the external micro sd, stuck the micro sd card in, booted in recovery and tried to recover with them... couldnt recognise them.
I also noticed that when trying to reboot, it came up saying that I didn't have root access... even though I certainly have for the past year.
I tried flashing an updated version of superuser as that was the suggested method on some forum - didnt help the situation.
Now when my phone boot loops, it goes straight to android system recovery <3e> and nolonger have access to CWM
No idea what to do, and my uni work greatly depends on me having access to my phone :/
Any help would be greatly appreciated
my baseband version is LRX21V.N9005XXUGBOB6
i got some problem ... it freak me oute but i founnd how to back my stock firmware backk
you shoud find your firmware ... it can be downloaded from sammobile.
and flash tar.md5 file via ONDIN.
good luck!
So, yesterday i tried to install Euphoria OS on my phone, but in all of a sudden, the /cache partition corrupted, i was dumb enough and deleted it via TWRP, making my phone fall into the QPST status.
After fixing it, i proceeded and reflashed KitKat, but the phone only shows 8GB instead of 16GB, so i tried to fix this by flashing TWRP, everything went well, until i upgraded to Lollipop again.
It always bootloops no matter what i do, i really need my phone with my 16GB of storage back, it isn't a Hardware failure since the QPST diagnosis didn't say anything about mobo failures.
I can mount all the partitions, i can wipe it all, i can boot into bootloader and recovery, i can do basically everything but booting the system.
Any light on this? it either happens after i flash TWRP or after i try to root it.
Im running Android 5.1.1 stock.
List of tutorials i have tried (In order): http://forum.xda-developers.com/nexus-4/general/wip-unbricking-nexus-4-using-qpst-t2208289
http://forum.xda-developers.com/nex...unbrick-n4-t2347060/post43164157#post43164157
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
Don't you dare tell me to reflash the ROM again, this is the first thing i have done, i did this 20 times already and it never worked. It isn't a ROM problem. It is a partition problem somewhere.
Fixed, had to use LGNPST to reflash JB 4.4.2, then upgraded to a ZIP version of the Lollipop ROM, then flashed the stock one.
I'm having the same problem with my Nexus 4. I read also about LGNPST, but I remember something about flashing the Optimus G cache partition I believe, then manipulating one of the prop files afterwards in order to get your 16gigs back. The problem is that all of the files needed to do this flash are attached to a stupid downloader site and so its full of pop up windows and adware from what I've seen. I can't get mine to boot into system, or bootloader, or recovery, etc. The device will not finish looping for debugging to be enabled, and even trying to boot into download mode is not happening. I've tried all I know to do, especially considering fastboot and adb both utilizeusb debugging. I really am baffled. Any root kits I've tried also don't work so far. Help please.
So... I f**** up. Won't bore you with the details, but the situation is this:
- /system is wiped, as is /data. There is no OS on the phone. Previously installed was B336. It's an L21.
- Can get into Fastboot
- Can also get into TWRP and/or the stock recovery, whatever is installed
- Can't get into Meticulus Recovery if I install it - just sits at the untrusted screen
- DLoad will not work at all. It's either stuck at 5 percent or quits with an 'incompatible' error immediately.
- When flashing a file, TWRP gives me a cryptic error message as to a missing META-INF thingy in the update.zip. This is new today because yesterday it just didn't work without multiple lines of red text. I have tried multiple update.zip from the original source, it's the same with all of them.
What I have tried:
- DLoading pretty much every firmware under the sun.
- Flashing Paranoid Android (which seemed to work but it won't boot beyond the untrusted screen)
- I tried CM too but it requires Meticulus' Recovery. Which won't work.
- Manually fastboot flashing recovery, boot, system, cust. This has worked on occasion but the install was stuck at booting up (at the Android logo). Now it doesn't work any more - FAILED. I can flash boot though.
- Hisuite... desperation. Nope, says it can't be used with the P9?!
- ... and of course eRecovery won't download and recover anything.
Kinda out of ideas here. Help?
You must first downgrade to stock MM.
You have to flash Revolution recovery, then the correct oeminfo (c432), after that you should be able to flags stock mm with the dload method.
Damn dirty oeminfo
Thanks buddy, that did it. MM did install via DLoad. On to new adventures!