Database Users

[Q] nexus 4 16gb version... after soft brick 5gb ???

hey, i'll be brief...
today (maybe yesterday for you.. nevermind) i was rooting my nexus 4 after bootloader unlocking... during the procedure my computer has freezed, so i rebooted it and after few minutes i tried again and this time i have correctly rooted my phone... then i flashed a custom rom and finally few hours ago i went into fastboot mode, erased all the imgs (userdata, boot, system, etc... don't ask me why i've done that, i'm very stupid...) and flashed the 4.3 factory image on the google site... and just now i've realized that my internal storage has switched from 12,95 GB to 5,6 GB...... I purchased the 16 gb version, but now i litterally have a 8 gb one... so tell me, is it a software problem? is it easily solvable or I have to ship the phone in warranty? please, answer me asap, i'm hopeless at the moment!!!
p.s. 5,9 GB is the TOTAL ammount that the os takes over, not the available..

I've had the same experience once,
Go to official android page, download the JDQ39 version and reflash it. Then optional for the cwm installation and others.
I had it a couple of times, so chillax.

yeah, i was already trying it... my router is very low-power now, so it is taking a lot.. omg this reassure me! ahahahahhaa i was going out of mind, thanks bro!

so is my device bricked? P5113

well the title says it all
but let me explain further
so ive been running cm10.1 on my galaxy tab 10.1 the P5113 model to be exact and ive been running the ICS bootloader and then on the cm10.2 thread i saw the JB bootloaders and decided to flash the P5110 bootloader......then everything hit the wall and pretty much broke D:
so then i wanted to try a few JB roms but upon rebooting to system on a lot of ROMs my tablet will just sit there at the device slash screen longer than usual then it will turn to a full screen of pink/green and a few other colored lines and just sits there ._. is it bricked? i hope not D:
what do i do? ive tried using ODIN to reflash stock to the JB firmware the same thing happens D: it seems that my device was fine on the ICS bootloader but ever since that update its been like this D: please help

have you tried kies? if not do this, BEFORE CONNECTING tablet TO PC start kies, go to upgrade and initialisation. enter your tablets model number and serial number. put tablet in download mode, NOW CONNECT tablet TO PC. this should force kies to upgrade your firmware

did that work?

A friend of me had same problem he solved it by going back to stock (rom & Kernel ) then he did a ota update and when the tablet said that update was ok he rebooted and he installed cwm and cleared cache and dalvic cashe and problem was solved

I actually got got running because it wouldnt boot even on an official stock firmware but for some reason it booted up after I went into the stock samsung recovery and wiped data factory reset so idk
Sent from my GT-P5113 using XDA Premium 4 mobile app

Factory reset is always the best initial move after flashing and getting a bootloop. When people panick and start flashing other things it drains the battery and corrupts files making i even harder to boot when a factory reset usually is all that is needed to fix a bootloop after a flash
Sent from my GT-I9300 using XDA Premium 4 mobile app

Can't get Modem in my 4.3 backup running, after trying 4.4 :(

Hi Guys,
I have used Jamals AOSP 4.3 v2.0 since it was available. Last week I have made a backup with Philz Touch of my 4.3 and tried to install Jamals AOSP 4.4 v4.0. I had to update the modem with Odin to make mobile connection work.
Now, I tried several times to get back to my backup of 4.3. Restoring the ROM is running perfectly, but the modem/mobile connection is just not working. After the start it doesn't ask for my SIM PIN, I get no mobile connection and Baseband-Version is not available.
I tried to flash several modems via Odin but simply none worked.
Today I made a full wipe and installed clean ROM of Jamals AOSP 4.3 V2.0 and it all went perfect and modem works. SIM PIN is requested and I get mobile connection.
I horrayed and immediately restored via Philz the proper Backup of my 4.3 from one week ago and again NO modem.
No matter what I do I can't get the freaking modem running when restoring my 4.3 backup.:crying::crying::crying:
I have no idea what to do and hoping for help here.
Thanks
Felix

DesireHDScreenorgasm said:
Hi Guys,
I have used Jamals AOSP 4.3 v2.0 since it was available. Last week I have made a backup with Philz Touch of my 4.3 and tried to install Jamals AOSP 4.4 v4.0. I had to update the modem with Odin to make mobile connection work.
Now, I tried several times to get back to my backup of 4.3. Restoring the ROM is running perfectly, but the modem/mobile connection is just not working. After the start it doesn't ask for my SIM PIN, I get no mobile connection and Baseband-Version is not available.
I tried to flash several modems via Odin but simply none worked.
Today I made a full wipe and installed clean ROM of Jamals AOSP 4.3 V2.0 and it all went perfect and modem works. SIM PIN is requested and I get mobile connection.
I horrayed and immediately restored via Philz the proper Backup of my 4.3 from one week ago and again NO modem.
No matter what I do I can't get the freaking modem running when restoring my 4.3 backup.:crying::crying::crying:
I have no idea what to do and hoping for help here.
Thanks
Felix
Click to expand...
Click to collapse
You dont have a efs backup?
Sent from my GT-I9505 using XDA

this should not be in the development section.the questions section is you know...........for questions

It appears for what ever reason that the modem isn't part of the backup. This happened to me today. I restored a backup using philz. No baseband etc. All I did was reflash my rom with without factory reset over the top of my restored rom. No data lost, baseband restored.
Sent from my GT-I9505 using XDA Premium 4 mobile app

HANDSY said:
It appears for what ever reason that the modem isn't part of the backup. This happened to me today. I restored a backup using philz. No baseband etc. All I did was reflash my rom with without factory reset over the top of my restored rom. No data lost, baseband restored.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Holy cow! That absolutely worked! You helped me to escape the KitKat hell and return to safe 4.3 haven
Thanks a lot and sorry for posting in the wrong section

DesireHDScreenorgasm said:
Hi Guys,
I have used Jamals AOSP 4.3 v2.0 since it was available. Last week I have made a backup with Philz Touch of my 4.3 and tried to install Jamals AOSP 4.4 v4.0. I had to update the modem with Odin to make mobile connection work.
Now, I tried several times to get back to my backup of 4.3. Restoring the ROM is running perfectly, but the modem/mobile connection is just not working. After the start it doesn't ask for my SIM PIN, I get no mobile connection and Baseband-Version is not available.
I tried to flash several modems via Odin but simply none worked.
Today I made a full wipe and installed clean ROM of Jamals AOSP 4.3 V2.0 and it all went perfect and modem works. SIM PIN is requested and I get mobile connection.
I horrayed and immediately restored via Philz the proper Backup of my 4.3 from one week ago and again NO modem.
No matter what I do I can't get the freaking modem running when restoring my 4.3 backup.:crying::crying::crying:
I have no idea what to do and hoping for help here.
Thanks
Felix
Click to expand...
Click to collapse
Same here, lost basebans and imei "null". Just odin and back stock is ok. From that time, I not restore 4.3 after try 4.4 anymore. Have to re-install for sercure.

happened to me too with both jamal 4.3 4.4
did the backup for nothing, i had to format the phone and start from nothing again with 4.3 and reinstall all stuff

Everything works fine, but when booting into recovery I get this tiny message in the upper left corner when the Samsungs Galaxy S4 Start-Up Logo appears:
Recovery Booting... (normal)
Recovery is not SEANDROID enforcing(red font)
Set Warranty Bit: Recovery (yellow font)
I think I get this since I tried to flash the latest Samsung factory image with Odin 3.09. Does anyone know what that means and how I can remove it
Thanks
Felix

Kernel-Version is 3.4.0
Build JWR66Y.S003.130805
Am I running the right Kernel for Jamals AOSP 4.3 v2.0 ROM?

[Q] Lost Gigs

I upgraded to Lollipop on my 32 gig Nexus 7 it shows that I have 4.6 gig free. What happened to all my gigs and how do I get them back?

mojimmy said:
I upgraded to Lollipop on my 32 gig Nexus 7 it shows that I have 4.6 gig free. What happened to all my gigs and how do I get them back?
Click to expand...
Click to collapse
Been seeing this posted a lot recently, seems the answer is to do a factory reset.

Yeah it seems everyone does factory reset to solve this, and that's fine if you don't care about keeping your data, but I'd first try just using fastboot to flash system.img from the stock lollipop 5.0 firmware. (I sideloaded the OTA and didn't have this issue.)

The issue is that user data is flashed instead of erased when you loaded the factory image. A factory reset reformats it and restores the correct partition size.

G4 Play OTA update from 6.0.1 to 7.1.1 fails

Hello,
My father has a Moto G Play (XT1602, reteu). It is currently running Android 6.0.1 with september 2017 patches. Build number is MPIS24.241-15.3-26.
The device is completely stock. No unlocked bootloaded, no custom recovery, kernel or ROM. Just a few small apps were installed.
There is a OTA system update to Android 7.1.1, build number NPI26.48-36. After downloading, it prepares for installation, reboots, and starts installing.
When the blue progress bar reaches about 40%, it stops and just says "Error". After some time the device reboots and says the upgrade failed, and no changes were made.
How can I find the cause of the failing update? How can I get the update to install successfully?

gewe said:
Hello,
My father has a Moto G Play (XT1602, reteu). It is currently running Android 6.0.1 with september 2017 patches. Build number is MPIS24.241-15.3-26.
The device is completely stock. No unlocked bootloaded, no custom recovery, kernel or ROM. Just a few small apps were installed.
There is a OTA system update to Android 7.1.1, build number NPI26.48-36. After downloading, it prepares for installation, reboots, and starts installing.
When the blue progress bar reaches about 40%, it stops and just says "Error". After some time the device reboots and says the upgrade failed, and no changes were made.
How can I find the cause of the failing update? How can I get the update to install successfully?
Click to expand...
Click to collapse
If the device is pure stock (never rooted) the problem lies with Lenovo/Moto. There is little you can do to self-address short of performing a 'factory reset' which may not (probably won't) help. Be aware all personal data will be lost.
A few tips:
- insure there is adequate free space for the update
- remove the SD card if installed
- try clearing the cache partition from stock recovery
Your best best may be to seek assistance from whatever carrier your father uses. Failures if this nature are not uncommon - especially installing a new Android version via OTA update.

I updated my phone today on 7.1.1 but my network is not working. Can't access calls/msgs. Can anyone help me?
Sent from my XT1609 using Tapatalk

zohaibkhan143 said:
I updated my phone today on 7.1.1 but my network is not working. Can't access calls/msgs. Can anyone help me?
Click to expand...
Click to collapse
Posting the SAME question in a half dozen threads does not endear you to the community or yield a faster/better response. I don't know the answer nor does anyone else here based on the lack of replies. Restore the backup you created before updating.

Davey126 said:
Posting the SAME question in a half dozen threads does not endear you to the community or yield a faster/better response. I don't know the answer nor does anyone else here based on the lack of replies. Restore the backup you created before updating.
Click to expand...
Click to collapse
The phone's bootloader is locked so I didn't make a backup now I wondering can I flash the previous rom again which is android 6.0 (241-2.35.1.17) or downgrading cause some issues?

zohaibkhan143 said:
The phone's bootloader is locked so I didn't make a backup now I wondering can I flash the previous rom again which is android 6.0 (241-2.35.1.17) or downgrading cause some issues?
Click to expand...
Click to collapse
Have no idea. Limited feedback suggest downgrading is not a smooth ride as bootloader/kernel was likely updated with the ROM. Hard brick is a possibility.

Davey126 said:
Have no idea. Limited feedback suggest downgrading is not a smooth ride as bootloader/kernel was likely updated with the ROM. Hard brick is a possibility.
Click to expand...
Click to collapse
Thanks I am expecting the same thing.

Davey126 said:
If the device is pure stock (never rooted) the problem lies with Lenovo/Moto. There is little you can do to self-address short of performing a 'factory reset' which may not (probably won't) help. Be aware all personal data will be lost.
A few tips:
- insure there is adequate free space for the update
- remove the SD card if installed
- try clearing the cache partition from stock recovery
Your best best may be to seek assistance from whatever carrier your father uses. Failures if this nature are not uncommon - especially installing a new Android version via OTA update.
Click to expand...
Click to collapse
The phone was not bought via a carrier. So the carrier will be of little help.
I collected some information from the phone:
Of the 16 GB ROM, Android uses 5,04 GB. Of the remaining 10,96 GB only 3,78 GB is used. So 7,18 GB is free. There is no SD card installed.
Of the 1,9 GB RAM on average 52% is in use. 0,9 GB is free.
Current build number is MPIS24.241-15.3-26, Android 6.0.1 with patches up to 1 September 2017.
The update has build number NPI26.48-36, Android 7.1.1.
When I was at my parents today, I forgot your last tip, about clearing the cache partition from stock recovery.. I will try to explain the instructions to my father.

I finally had a chance to clear the cache partition. Unfortunately this does not solve the problem. Installing the update still fails.