Hello,
This is going to be kinda long, I want to give all details I can remember in case it helps.
I decided this morning that I was going to try out the unofficial CM11 rom for Galaxy Nexus GSM. So, first thing I do is a backup from Clockwork Recovery (latest touch recovery flashed).
After that, I flash the rom, and the gapps. I reboot to see if it works, and after 5 minutes of use everything looks pretty sucessful.
So, adb pull my backup and offload it to my computer in the case that something goes really wrong, because I'd like to get a clean start. So, I wipe the device as completely as I can in Clockworkmod Recovery. I then adb push the cm11 rom and the gapps roms referenced above. I use Clockworkmod Recovery to flash those onto the device, reboot and start playing around then realize that I have no cell service. Try manually registering on my T-mobile to no avail.
I think this is a baseband problem, so I fastboot flash radio (stock nexus radio rom from 4.3), reboot into the system and still no service.
Then I begin thinking my phone radio has completely failed, so I take a simcard from my girlfriend's phone pop it into mine, reboot and still no service. Reinstall my original sim card.
Then I am REALLY thinking my radio has failed, so I figure I'll just flash the full 4.3 stock suite in case I'm missing something small because I don't understand how something works. Still no service.
So, as a last resort, I push the Clockworkmod Recovery backup back into the /sdcard/0 directory, restore in Clockworkmod Recovery, reboot and it works(!).
Now I start wondering what I'm failing to understand about this problem, so I go ahead and do a factory reset in Clockworkmod Recovery and back to no service(!).
I really thought I understood how it worked, but I must be missing something here, or maybe Clockworkmod Recovery is wiping something it shouldn't be? The final thing I can add is each time I fail to get service in the installation, the service bars light up for 1/2 second to 2 seconds during boot. Maybe someone could help me spitball what's happening here?
Thank you very much in advance.
I think all yu must do is download the latest stock firmware ment for for your device.. from internet.. and install that properly on yur device.. this will do every thing right.. see I too am not at all good with using programme stuff and so.. therefore I keep the copy of firmware with me always.. that helps when I almost destroy my phone
tc and good luck..
---------- Post added at 04:01 AM ---------- Previous post was at 03:56 AM ----------
and it might be possible thet the rom which yu are trying is not ment for your device version.. chack that too correctly..
Problem found (not yet solved, but that's another question)
OK, I found the problem. My non volatile memory got corrupted. I pulled an image from the EFS nv memory partition devfs file, mounted it as loop on my localhost and got nothing but a lost+found directory. It's not a terrible thing, but from now on when I wipe this phone, I will need to adb push my /data/radio backup to the EFS nv memory partition. That is, at least until I find out exactly what I need to do to reconstruct the memory partition. Shouldn't be that hard, but I really need a good description of what is in all the EFS memory partition files for the Galaxy Nexus. :good: I'll dig around the forums a bit, maybe ask someone for the directory structure, maybe I'll be able to, at least, partially restructure that memory partition with a good old dd'ing. Maybe I'll root my girlfriend's Galaxy Nexus so I can get the structure proper.
Hope this helps someone else!
Related
Hey guys. Forgive my noobity but I could do with some help and might have a unique problem although I dare say someone has had this or similar.
Firstly, after putting a 64GB stick in my tablet the other day, it all went badly wrong. I had done it before with my previous 64GB that had been playing up so I sent it back and got a new one. The new one seems to be where it all went pear shaped. I might add, the 64GB is for my phone really but my phone cam was playing up so I was swapping it over and stuff... anyway the card itself seems fine in my phone.
Anyways... now my ampe tablet is suffering some strange effects that have changed. initially it would not boot up unless I redone it with the official firmware.. but then wouldn't boot up again, unless I did the same thing over and over. then one time it just refused to boot up past the initial boot screen. I gave up for weeks then picked it up again two days ago.
Now I give it the firmware installed using pheonix again and it booted up. Ahh I thought... lets play. Now I plug it into the pc but the pc says I need to format the 5GB internal partition. So I did. I then looked how to fix the fact that the tab still says it has 0.00kbs internal storage in settings. Then after a while it came up saying 5GB so i copied some files onto it.. great. But I still can't install apps as I found when trying to do this tested working fix http://www.youtube.com/watch?v=sJlpek6w624
I then read about using android commander to move busybox from xbin to bin in the system folder but mine is already there.
So now I am stuck. I can't test if my tab is rooted for the youtube link fix above although this is what I said to Nayeem on youtube:
================
Hi Nayeem. I'm really struggling with this. At first my tab was staying at the 2nd initial boot up screen after I put in a 64GB SD card. Using pheonix I managed to get it to boot by reinstalling the updated official rom from szampe but every reboot back to square one. I left it alone for weeks and came back to it, reinstalled the factory rom again and now it will boot up everytime but it has factory reset every time. I cant run the apps you supply for some reason. Everytime I have rebooted the tab, and connected back to pc it says I need to format the internal 5GB partition. I don't know if I have rooted it properly as I can't check. The commands you give above, work as it changes the location proven when I 'get' it. I'm really stumped. I'm trying out a method someone said about moving busybox from sys/xbin to sys/bin but it's already there (using android commander) so I am really stumped now. When I format the partition, it allows me to copy files to it.
================
So far I am stuck with boot up being a factory reset and the partition needs formatting and although the tablet seems a little laggy, everything I have tried works including wifi and incoming email alerts after logging into google account for playstore but no apps will install or update. the best warning I get is there is no memory to install anything and Nayeems method of moving the install location to the sd card seems to work but nothing will install still saying NOT INSTALLED when I try.
Sorry for the long winded thing but I am really new to all of this.
My hat is off to you if you read all of this and can offer a solution so i can give this tablet back to the kids.
Do you have an installed recovery
Try installing a recovery and wipe data and cache. If it does not work u have to repartition ur tablet
nelsontky said:
Try installing a recovery and wipe data and cache. If it does not work u have to repartition ur tablet
Click to expand...
Click to collapse
I am gonna look into this tonight and see what I can find out. I really don't know exactly what I am doing outside of getting pheonix up and sending a standard rom back to it as previously mentioned.
How would I repartition it ? Sounds stupid asking as i can build pcs... just want to make sure I am doing the correct method.
Hey folks,
have a huge problem here. I think i erased all the data of my girlfriend's phone -.-
I just wanted to clear her phone by setting it up with a custom stock rom withput bloatware.
I started to unlock the bootloader and flash a new recovery because i wanted to do a nandroid backup and use titanium to backup her data. But the problem started here. Her phone had the 4.4.2 OTA update --> HBoot 2.22 but I flashed TWRP 2.7.0.0 instead of 2.7.0.5 because i didn't know the fact that the partition layout changed. After flashing the recovery the internal sd card couldnt be found and twrp said "no OS installed" when i tried to reboot to the system. Well, the phone did boot to the system, but i think it made a background factory reset i didn't want to do ...
So now i had a clear System running, no apps, no contacts, nothing. At this point I didn't look at the sd card if the data there is erased, too.
I thought, when i flash a recovery which finds the sd card, maybe the system will be restored as before this procedure. So i flashed twrp 2.6.3.0 but again, no sd card. After that i tried cwm 6.0.3.6 (because i didnt know that there was a 6.0.4.7 ...) and cwm accepted the card. So i booted again into system but still there was a clear stock rom, with ... nothing.
THEN I looked into the sd card and ... nothing. Empty, everything got deleted, only the new made folders where there. No Pictures, no Music, nothing.
My girlfriend gonna kill me ...
I tried to rescue the data from the sd card, but different apps found nothing then the data, that is already on the sd card. No old pictures or old music. Thanks to MTP, i can't run a datarescue at my pc (or can i?).
Do you have any idea what i can do now? Is there any chance of getting the data from the sd card back? Or better, getting the old app data back?
Please help me guys, you are my last hope.
greetings,
patrick
best of luck to you my friend
Im in the same exact boat to the T !!
Did the same thing almost identical to you , all because the development is so shabby and unclear with this particular phone its pathetic.
twrp website shows the latest recovery.img as 2.7.0.0 No mentioning of flashing a newer version
Theres only one thing at this point you can hope for Find the stock 4.4.2 ruu utility and run it... or get her a new phone.
Ive been at my pc for 8 hrs going blind and im done ill toss it before i spend another hour searching for a fix
I have multiple posts Noone cares here.
And i dont believe htc has the 4.4.2 ruu out yet
Well, my problem was not to get the phone running, because it did "repair" itself.
My problem is the lost data
Hi Patrick
Having no backups and starting to change things in software is always a bad idea. Mobile phone, PC, etc.
On the other side, there are very nice tents today in case your girlfriend has locked you out of your home now
Consider it from this side, you tried something and bungled :crying: the phone/data - hopefully others will read this before they install the "old" recoveries on their new Hboot.
But I totally agree with you, these unofficial versions of the recoveries are really hard to find. As I was looking for the download link I've chosen the way through the xda thread.
regards
Thanks for your thoughts
But luckily my girlfriend doesnt lock me out of home, because i had the backup from November
Since then we didn't have made any greater activities so no real important pictures were made since then.
I thught of making a "newbie friendly" thread with important information about hboot 2.22 and the "hidden" recovery's from twrp and cwm.
Maybe this can help others to prevent such mistakes I did in the past.
Klivarre said:
Thanks for your thoughts
But luckily my girlfriend doesnt lock me out of home, because i had the backup from November
Since then we didn't have made any greater activities so no real important pictures were made since then.
I thught of making a "newbie friendly" thread with important information about hboot 2.22 and the "hidden" recovery's from twrp and cwm.
Maybe this can help others to prevent such mistakes I did in the past.
Click to expand...
Click to collapse
Would be good to have this info in a sticky, as these posts can get buried easily.
Sent from my GT-I9000 using Xparent Green Tapatalk 2
Hi guys, I just registered @ xda because it looks like it's the only serious and feedback active community available. In 10 minutes I found most of the info I was looking for, but I still want to make sure what Im planning to do is fine before I mess up again. Here's the issue:
I was fooling around with the tablet and had just rooted it so I could get rid of some bloatware, and decided to go further and install cyanogen, just for the looks. So I got this thing cm-10.1-20130411-EXPERIMENTAL-p3110-M3 from the official site, which was I put on a folder inside the tablets storage (not on the 16gb SDcard it had in it). I downloaded Rom Manager and skipped through the "search and download rom" and went for the option of looking for it inside the SD card. I had the Backup options and the wipe cache and data ON.
So I proceeded and it booted, started to do the backup and at some final point it had an error, something like "could not backup Data!". I had the options of rebooting, some other stuff and the option of installing a rom from the SD Card. I went for it and searched for the .zip inside the storage, and installed it. It did it withouth trouble, and when it finishd it prompted me to install an update, which I didn't (don't know why).
Then, I went for the reeboot option and when it started I get the normal samsung's black screen with the device's name on it, but then I get a fast glitching image that sweeps through the screen and the cyanogen startup logo which gets stuck for ever.
Click to expand...
Click to collapse
Now Im past it, I can get to download or recovery mode, so I moved onto getting the original firmware so I can clean-install again. I got it from sammobile, chose the one belonging to Chile (that's where I got the tablet), and it's 729mb of data. The tablet is a Samsung Galaxy Tab 2 7.0 P3110
If I flash it with Odin will everything be fine? All I have to do is that thing in downloadmode when I rooted it, but with that 729mb file? Should I put it in the external SD or is it more convenient to place it in the internal storage?
I appreciate your help in advance, I know this is as basic as it gets but messing up again would cost me dearly, since I have to do other stuff.
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
billysam said:
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
Click to expand...
Click to collapse
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
aguscanzani said:
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
Click to expand...
Click to collapse
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
billysam said:
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
Click to expand...
Click to collapse
You guys have helped me a lot. I've worked everything out and now i've got to reinstalling android on it, AOSP's 5.1.1 Lollipop. It's beautiful. There's just one problem: Since it came with no apps at all, I wanted to install everything on it again. Problem is, when I go to google play, it shows that i've already got my apps installed, so it wont let me download them, and it doesn't matter if I place the APK's inside the tablet as there's no manager to open them. Even if I download apk's through the tablet's own web browser, it says it can't open the file. Any ideas on this?
Edit: Solved, see bottom
ROM (D6633_Customized HK_1290-5630_23.4.A.0.546_R6C_HK_SuperSU2.46_XZDR2.8.21-signedv2)
Bit of a dumb move on my part. It all started when my snapchat stopped working, I updated, and then Titanium Backup wouldn't restore the data properly (giving me "parse error"). I was trying to fix that and read online that sometimes this is caused by improper permissions, so I booted into recovery mode, couldn't find the option, but somehow decided "hey, maybe my root permission (?) is wrong slash it's 6am and I just watched a wild 2016 election end" and I hit the button. Now my phone is stuck in a bootloop.
So my question:
1) What exactly does re-root phone do (in CWM), and why would that have messed me up? Is it because I have a pre-rooted rom?
2) I wiped cache and delvik and it doesn't help
3) How do I fix this? I was thinking of loading a SuperSU zip on the SD card from my computer and flashing that, assuming somehow a corrupted root is at fault. I can't seem to get the thing in ADB mode as a side note.
3b) If that seems like a good idea, does it matter what one I use?
4) If I reflash the ROM, it should keep my apps and stuff, ya? I don't actually care if my phone is crippled, I just need it to work long enough to properly back up some media, and mainly get my whatsapp over to my new SIM card. If I can't get in it's forever stuck on my old number which I don't have the SIM for anymore.
Any help would be GREATLY appreciated.
Edit: I don't know how to delete this. Anyways, with other resources I found out that because I used a pre-rooted ROM, there were issues with using CWM to try to do the rooting with its built in functions, softbricking the phone. Reflashing the original pre-rooted ROM worked fine.
So here is situation.
Phone been running 8.x version of havocos for months, however I was never fully happy due to broken usb tethering and random lockups (blue light freeze).
I decided to work on the phone 2-3 days ago, this involved doing a manual backup of all of data/media, and a nandroid backup. As well as some exports of configs in tasker etc.
I then flashed OOS stock, and nolimits, discovered tethering was still broken (yet it works with same sim in samsung galaxy s7 and hauwei).
This was the only issue tho, everything else was functioning as expected, phone was still fast.
Then I needed quick access to something that was on my phone from havocos, so decided to do a nandroid restore, this nandroid backup had all partitions ticked. The restore I also had all ticked.
The restore failed with an error 255 during data restore, I googled and found out is a nasty known bug for 2 years on TWRP, this backup was done on 3.2.3, I know now is a newer 3.3.x where this particular bug with corrupt backups might possibly be fixed.
I decided to try and boot havoc anyway but it boot looped, so I then went back into TWRP, and restored the vendor partition which was skipped. As it stopped on data, still boot looped, but also now this created a device is corrupt error on every rom boot even on stock OOS.
I spent ages trying to fix this error and during the process, discovered my phone no longer can be detected in flash boot as a com device in windows so currently the phone cannot be used with the MSM tool.
Eventually I reflashed stock using a flash-all script from here, and also put back on twrp using that script, and noticed even more issues that were not there before.
1 - phone is now much slower, stock before booted in one second after first boot, now its way way slower. Over 10 seconds so 10x as slow.
2 - I think before was a cache partition but is now gone. Supposedly these arent a thing anymore tho.
3 - nolimits zip will no longer flash with an error 1, I did exact same process as before but simply doesnt work now, the twrp detailed log right before the error 1 says "Please install the latest Magisk!" which suggests its failing to detect magisk.
4 - camera app is way slower, and OOS feels slower, laggier in general than before the problem.
5 - MTP no longer works when phone is booted up, again this is stock OOS and even if phone isnt rooted no magisk etc. But still works in TWRP. Basically the device pops up, I can see internal storage, but the size information is missing, and is no visible files/folders.
From what I can see I think my EFS is fine, I see an imei number.
I did fix the corrupted device error using a reboot command someone posted in that thread, so that error is gone now at least.
Try to flash oxygen os beta version from the official download links, let it install the stock recovery, then boot into rom, finish the installation progress by just skipping it and then factory reset it twice from recovery mode.
after doing that and finishing the setup , try to take picture and see if its saves it to gallery ( if the picture delete it self try to factory reset it through recovery for 1 more time)
I think you have figured out whats wrong, it just clicked, and I went to post and found your post so sorry no reply yet.
Indeed the problem seems to be a lack of /data/media/0
I have multiple times wiped data, and twrp has been putting files directly in /data/media, I just discovered I Cannot even take screenshots, magisk cannot download modules as well.
So I guess the stock recovery creates this structure?
Pretty shocking that twrp doesnt fix this or even have an option to. I will report back and let you know how things go, thanks.
Issue still there after stock recovery reset, wow these phones are damn hard to work with.
Also it seemed to do nothing, no settings were lost etc.
So basically stock recovery even if I choose full wipe does nothing, there seems to be some kind of lock on the internal storage that anything made by one plus is refusing to write.
I wonder if this is due to the device is corrupt message I had before where it said the device can no longer be trusted.
I can confirm that files that are on there are now visible in file manager and root explorer. But file manager can do no writes. root explorer can create new stuff but cannot delete or overwrite anything there, gets access denied.
I propose to start over again following this guide, option flash-all-partitions.bat. Helped for me.
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
@chrcol ..., but you've issues
chrcol said:
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
Click to expand...
Click to collapse
In recovery, format data. Problem fixed. Wipe will never fix your problem but format will.