Ok so the other day i pulled my charger out and my phone froze so I pulled the battery and ended up getting the boot loop.
So i searched around and found you can flash it with odin. I tried flashing the stock files but they fail i try flashing the stock package and fail the only 2 that work are the froyo debloated and the froyo super clean.
so now i got it booting up but everytime i turn it on it goes to the new setup and doesnt save any contacts or anything and i cant download anything off the market cause it says 0 internal memory.
I found a thread on it and tried what it said but still didnt work i tried adb shell and parted and permissions are denied.
somehow the partitions must have been erased either when it first messed up or from me trying to fix it.
Im just trying to get back to my stock.
Ive searched almost every thread and cant find an answer if anyone could help id really appreciate it.
Related
Hi, I've had lot's of problems with my HTC recently, no adb access etc, device not being recognised and recovery playing up, ie not being able to wipe install roms etc... however I fixed the recovery issue and managed to do a nandroid backup, I put on I think it was 1.5 HTC sense hero rom... and recently realised that i can only flash 1.5 roms, not 2.1 anymore? would any developer know what would of caused this problem? Any 2.1 rom just locks on the Hero logo, and I've left it for over an hour in some cases and nothing happens. Again, I used to be able to put on any custom rom.... I'm all out of ideas.
wipe
did you wipe? what recovery image you using etc etc?
1. post in the correct section.
2. remove the ext4 partition from your sdcard, or change it to ext2 or ext3.
3. get adb logcat, otherwise this is like the question "my car won't run, can anybody tell me why?"
I have wiped numerous times... sorry for the "my car won't run type question etc...." just that I've done my research, gooogled, posted detailed info previously on here and another forum, I even fixed my own problem of the recovery image, without fixing that I would have nothing. But anyway the card is partitioned with swap, ext2, fat32 using the latest Amon_Ra image 1.6? something... i've spent weeks trying to resolve this and learnt a lot along the way.
Obviously not where to find the adb logcat... don't worry I'll google it.
Apologies for posting in the wrong forum, if it can be moved could a mod do so?
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
bonesy said:
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
Click to expand...
Click to collapse
Thanks for your reply, I will approach this method again at some point and give it a try, but I think I read somewhere that I couldn't do it for whatever reason, but I'll look into it again seeing as you've had the same issues. Thanks.
bonesy said:
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
Click to expand...
Click to collapse
Actually I believe I didnt attempt this because I was no longer able to get my HTC hero working with ADB, as soon as I plug the device in, it comes up as device unrecognised, so I think goldcard method it out.. :-(
on the risk of offending you again (even though i am trying to help here...): you did not provide really much valid info. for most things you just said "doesn't work". what happens if you start by pushing home+power? saying the recovery doesn't boot up tells what does NOT happen, for a diagnosis we need the info what DOES happen.
anyway, if i get you right your recovery is now working. now repartition your sdcard (ext2 and fat, NO swap), do a full wipe, then install the rom you desire to use, then move the log to sdcard ("other" in recovery). reboot your phone and execute "adb logcat > c:\logcat.txt" on your pc. if it doesn't boot up after five minutes stop logcat with ctrl-c and post the two logfiles (recovery.log and logcat.txt). you need to set up adb, if you have problems with that sort them out, there is no way to get any information about your problem without the log.
oh, and about the goldcard: i don't know too much about goldcard'ing, but i can't see how this should help here. my strongest guess is that the swap partition interferes with the boot process...
No worries no offence taken. Pushing Home+Power works and takes me to recovery. Back+Power takes me to bootloader and USB Bootloader device is recognised, so I am able to get Fastboot.
Just recently installed stock rom, to see if that solved the USB and ROM issues but no such luck, re-rooted, put anom latest recovery back on, and went on to do what you have advised to help.. i've attached only the recovery.log in zip format only, as when doing adb logcat command use mentioned(after installing new rom), all I get is "waiting for devices" whilst the phone is stuck on the Hero logo, I waited about 10 minutes, exited from the adb, and the log file was empty as I guessed. I've tried every possible way that I found on the web to try and get the ADB function working again and I realise this is important to get some info.. but I've ran out of ideas for that.
Maybe the recovery(attached) may show something, all I noticed is that the cache and something else was not wiped for some reason? If you or someone has time, have a look through maybe someone knows what is going on.
Thanks for your help and patience
This has probably been covered here previously, but i searched fro several hours and tried several different things before giving up and just asking...
I have an 8gb NT, and i was running CM7 on it. I installed CM7 with Clockworkmod on an SD, but i had installed TWRP locally on the device. I was going to flash CM9 on to the device today, so i turned it off and went to boot into recovery mode, but i quickly noticed that there was something wrong with cyanoboot. It just boots in to recovery, there is no menu, just a loop. In TWRP, everything i try to load comes back with a "can't mount..." error. I read in several places to try certain rom installs through clockworkmod, so i booted to the SD card, but that doesn't work either. I think it is probably an error with the partition tables, but i was unable to find anything telling me how to repair that, though i found a lot of places and articles that said that it can be done. Does anyone know what might have happened here, and more importantly, how do i fix it? At this point i would be happy to go back to stock if i could...
Hi guys, firstly I'd just like to say I have followed all the protocol that is required on here and been reading and researching/ applying fixes for the past few days now. I have tried to help myself as far as i possibly can but i am still having no luck and i don't think too many people have had the exact similar issue after reading all the other threads that are similar to my issue.
with some of the fixes it is my first time using them as i have never needed to in the past, so bare with me if my level of understanding isn't as great in some departments.
Now onto the issue:
I own a galaxy s3 i9300 and it has been rooted on stock rom since day 1 about a year ago. A few days ago my phone battery died, and when connnected to the charger it had this grey icon with a circle. It wouldn't boot up either so after searching on the net i thought i would listen to the advice of clearing the cache etc etc but this didn't work and neither did the wipe data/dalvik in CWM.
So i reflashed a stock jellybean rom and it worked fine.
It was then at this stage i thought i might as well upgade to a custom rom as every galaxy i had owned before i had done it on, and my current Note tablet is also running custom rom.
I first loaded a stock 4.3 rom and then flashed the slimbean 4.3 with gapps ...and it worked perfectly. I found a couple of issues with the browser which i use a lot so i downgraded to a 4.2.2 version of slimbean with gapps and this made the browser really fast again and all was perfect.
I had been using this for two days or so and everything was smooth, including charging etc until one night it had that same grey battery icon again with the circle and would get stuck booting at the samsung logo.
So as this had happened before i thought i would just flash a stock rom....this is where it all started going mad
Bearing in mind, every flash i always did it properly and wiped cache/dalvik cache and wiped data three times for each one just to make sure as i didnt have anything of value so wanted a fresh wipe each time and didnt need to back anything up.
now before i get flamed i realise i made a huge stupid error in not backing up my efs folder before hand as i had done with every previous phone but because i was under pressure to get it working it skipped my mind totally.
So i flashed a stock jellybean 4.2.2 rom and still bootloop with the EFS not found invalid argument error
i flashed a 4.3
i flashed a 4.1
i flashed a different 4.1
i flashed a different 4.2
i tried loads but nothing worked
so after reading that this would not help as it doesnt touch the efs i looked into fixes that others had done
i tried to follow this http://forum.xda-developers.com/showthread.php?t=2197515
So i downloaded efs professional / adb tool
i downloaded busybox
and cwm was already on the phone but i downloaded philz cm incase i needed that too
now as the phone doesn't turn boot up i can't access anything, i can only access download mode and CWM.
When i open efs professional it says current device offline, turn on allow usb debugging to confirm your phones RSA fingerprint and click ok.
I have no idea what to do about that because i can't get into the phone.
Regarding busybox i have no idea how to get that to install on the phone, i have tried writing some stuff to push it in the adb shell (but because its my first time using adb shell and command prompt i have no idea if i am doing it correctly). Can you install it with odin?
also regarding adb shell i followed the guide http://forum.xda-developers.com/showthread.php?t=2197515 and got into [email protected] and SU....and then when on the phone in cwm i clicked mount efs...and obviously it failed. I went into the log as said and /dev/block/mmcblk0p3 was the file it failed to mount
the thing is everything after that step doesnt work, as i can't create an image of mmcblk0p3 as it says it can't find it as if it doesnt exist.
So im screwed as it effectively is saying i don't even have that file or efs folder i think?
The thing is i never had any issue with losing imei or anything like that at all and this just happpened out of the blue without me doing anything as such
any ideas?.....would be HUGELY appreciative for anyone willing to take the time out and help me with this as i'm not sure i can explore any more avenues on my own with my limited knowledge and at the same time don't want to give up.
PS. I also have access to a galaxy s3 i9305 ....and can possibly try and source another i9300 from a family member IF this helps in any way or makes life easier?
Stickied faqs and guides .
No IME/ EFS
service centre repair is your best choice if you have read and tried the stickied fixes .
Reads like efs partition corrupted and your phone was already suffering with nand memory issues.
There is no substitute for an efs backup, you cannot recreate the unique information it contained.
Take it to a reputable repair centre, they will be able to get it back to normal, but you are still left with why it keeps corrupting -which may require a new motherboard.
Sent from my GT-I9300 using Tapatalk
Mod Edit
Please refer to ,and post in the stickies in the General section.
Thread closed
malybru
Forum Moderator
Hi, wanna make this quick and short as possible.
Im new here, and I need help on my new phone.
yesterday, I got a Lenovo A369i phone that happens to be a secondary phone for me. So as advntureous as I can be, I tried doing what some of my friends do... Custom Roms. Im not a pro in regards with these stuff, but I aint no noob too, Im a bit literate bout these, but not knowledgable enough to fix this.
so heres what. Phone is Lenovo A369i.
Build no : A369I_ROW_Lite_S005_140823
Android 4.2.2
Rooted and Stock ROM atm.
I came across a site, lenovoa369iblogspot.com, and saw lots of Custom Roms and whatnot and saw a easy way to root and flash my device w/o pc. Using Framaroot to root and MobileUncle Tool for TWRP recovery then installation of my desired ROM. I followed the steps correctly, was able to ROOT(i had SuperSU and was able to use Root-Required apps) and had access to TWRP.
Now, it was instructe to wipe cache and factory reset, which failed at first(but I didnt noticed it caused I acidentally pressed back, and thought it was successful) then I continued installing my ROM(it was a Samsung S5 ROM) it started OK, until it was extracting, then it stopped. At first I thought it hanged, but it just got screen timeout. I left it there for 30mins and I thought it was done. Upon reboot, I noticed nothing changed and speculated something went wrong. So i browsed the web for other ways to install and flash my phone cause I thought it just didnt work. I tried getting a stock rom with build no. S110 and tried some ROMs too but cant get it to work. I also tried switching to CW and TWRP v.v. but cant seem to update/install it, until I noticed that I cant wipe my cache, data or anything on my phone through recovery at all. I can still access my External SD car, cause that where all the ROMs are placed, but as i try each ROM, there would be a bunch of errors like E: cant mount emmc, cant mount sdcard, cant mount cache etc etc. So even I cant do factory reset cause itll say it Failed. Maybe its the reason why I cant install those ROMs. I tried unrooting, no good. I tried to update the software through settings, but after download, it still goes through TWRP/CW and still cant install together with the cant mount errors. I tried the MOUNT on TWRP but i xant mount anything except for the External SD card. It says on the emmc "Emmc=0bytes" like there wasnt an internal storage to begin with. And its really frustrating cause I cant even do a factory reset even through settings, it still redirects me to Recoery Mode. Tried using TWRP/CW and even android stock recovery and to no avail. Funny thing is, I can sill access the memory, I can format the Phone Storage(1gb) and still have the internal storage(1.2gb) for a total of 2.2gb(even tho it says 4gb in the box, I think 2.2gb is the only usable memory) I can still access its file, save and do stuff. Heck, theres nothing actually wrong in my phone, all features are still there BUT I cant make a Factory Wipe cause of that Mounting Error. I want to fix this so I could finish installing the ROM i wanted and I also want to be able to factory wipe my phone incase I do something else stupid.
I really dont know what to do, its been hours since I started looking this up. I also fried flashing it on PC but it wont succeed cause when i start flashing, even tough it "kinda" detects my phone, the Flash Tool still shows my emmc=0.00 bytes. I dont know if this happened when ai was starting to root my phone or during the initial installation of the ROM, so I rally dont know what to do or think of. So I resorted to ask the real pros for help, cause I get OCD on these kind of stuff and I cant sleep or do anything until i figure this out or find a way.
Hope someone an help me. Thnks!
P.S., i dont have access to my PC right now, so I only have my other phone and tab. Im also not much well versed in advanced programming whatnot, I only know a few basics so please spare my brain on codes XD I need something in english if thats ok Thanks!
P.P.S. Sorry if this is not the appropriate place to post, feel free to move it if needed. And I also tried posting on the site where I got the ROMs and stuff, but Im afraid the last post was like months ago so I cant really hope for them to help me.
So I have read through a lot of threads on here already about similar issues. But I cant find an exact answer to the problem Im having. I tried to get more space with my sd card so i downloaded foldermount, and I gave it access to external sd and rebooted. When I rebooted it stopped at the metropcs welcome screen and did nothing, I immediately knew it was soft-bricked. I tried taking the battery out restarting and still same problem. So i rebooted into TWRP recovery and instead of just getting my laptop and googling, I tried to factory reset but somehow i erased my rom because it said "No OS installed are you sure you want to reboot". So now it wont even go to the samsung screen or metropcs screen. it turns on but thats about it. I hooked it up to odin and flashed a stock rom but everytime i try, it stops at sboot.bin and then fails. I read that this is a problem with bootloader and imnuts has solved this proble, but he only did it for other phones, SO BASICALLY I NEED A BOOTLOADER FIX FOR STOCK ROM FOR SM-G550T1 (SAMSUNG GALAXY ON5)????
Have you tried to flash another rom? How long did you take your battery out for? In twrp, do you have adb access?
ramiabouzahra said:
Have you tried to flash another rom? How long did you take your battery out for? In twrp, do you have adb access?
Click to expand...
Click to collapse
Yes, I have flashe three different roms now. I have the same issue every time. And i took the battery out for a few minutes but i dont think thats the issue its that I'm missing an operating system. And in TWRP i do have adb but i forget what ADB does.
Also, with the help of youtube, I created a nobootbinrom.tar or something like that and flashed with odin to no avail. It was a complete waste of time.